Skip to main content

Split Fees

POST 
/feeSplits/splitFees

Estimates payer-side recoup/surcharge and merchant-absorbed fee splits for card, bank, and related rails using the merchant's Fees & Incentives configuration.

Returns payerTotalFees, merchantTotalFees, and feeSplitType — these describe checkout/principal split, not finalized card-network merchant processing fees (see List Fees and Fee Events).

Paystand resolves the applicable fee setting plan (default plan, feeSettingPlanId, payer, invoice/receivable context, or feesIncentivesUrlKey) using the same logic as checkout — you do not need to build fee rule objects manually.

Use this before capture when your ERP needs estimated payer fee lines (for example $500.00 principal + $15.00 payer fee = $515.00 payer total).

Recommended request for receivable checkout: include provider (receivable), payerId, and invoiceId (receivable ID) so Paystand resolves the correct Fees & Incentives plan — subtotal and currency alone are not enough for plan-aware estimates.

Example:

{
  "subtotal": "500.00",
  "currency": "USD",
  "provider": "receivable",
  "payerId": "{payer.id from payment or payer customer}",
  "invoiceId": "{receivable.id}"
}

After payment, read feeSplit on Get Payment for actualized payer-side split; use Fee Events or embedded fees[] for merchant processing fees. Card flows may still emit additional Fee Events after Posted — see Payment and fee reconciliation.

Auth: Merchant API credentials (Authorization: Bearer + X-CUSTOMER-ID). This is the server-side integrator route (/splitFees), not the checkout publishable-key route (/splitFees/public).

Request​

Responses​

Per-rail fee split estimates