Payouts and fees
Pay out your merchants with Ginger Payout: payout configurations, schedules, bank accounts, price plans with IC++ or blended fees, rolling reserves and adjustments.
For acquirers on Silverflow. Your merchants want the money from their sales in their bank account. With Ginger Payout, your platform pays them out itself: it collects their settled transactions, deducts fees, refunds, chargebacks and a rolling reserve, and transfers the rest to the merchant's bank account on a schedule. You decide the schedule and the fees per merchant. Your Ginger contact switches Ginger Payout on for your platform on request.
Ginger Payout handles transactions processed through Silverflow, in euros.
Payout configurations
A payout configuration (a payout entity in the API) is the unit Ginger assembles and pays out. It has a scope, a schedule, a bank account and a price plan.
Scope. A configuration applies either to the whole merchant (one configuration for all its projects) or to one project (one configuration per project). A merchant uses one of the two, never both. The scope is fixed once set: to switch, remove all configurations of the merchant first.
Schedule. How often Ginger pays out:
| Setting | Meaning |
|---|---|
| Frequency | daily, weekly on a day of the week, or monthly on a day of the month. Days 29 to 31 fall back to the last day of shorter months |
| Per-transaction delay | Days between the completion of a transaction and the moment it can be paid out. Gives refunds and chargebacks time to arrive |
| Cutoff time and timezone | The end of the merchant's day, such as 23:59 in Europe/ |
Bank account. The account holder, IBAN, BIC and an optional description that appears on the merchant's bank statement. You can create a configuration without a bank account: Ginger still creates payouts, and transfers them when you add the account.
Price plan. The fees Ginger deducts, see Price plans.
Changes to the schedule, the bank account and the price plan create a new version. Payouts already in transfer keep the bank account that was active when their batch settled.
When a transaction is paid out
A transaction is paid out once the processor has settled it: Ginger waits for the transaction to appear in the processor's settlement report, with its scheme and interchange fees. Sales, captures, account funding and original credit transactions add to the payout; refunds and chargebacks are deducted. Authorisations and voids move no money.
Readiness
The Admin portal shows whether a configuration is ready to pay out, and what blocks it:
- No price plan configured.
- No bank account configured.
- Some transactions are still awaiting clearing.
- The project or the merchant is inactive: payouts are paused.
To stop payouts for a while, pause the configuration (status inactive); resume it to continue on the schedule.
Price plans
A price plan is a list of fees. Amounts are in the smallest currency unit; percentages are strings with two or three
decimals, such as "1.50".
| Fee | What it charges |
|---|---|
IC++ markup (ic_) | Passes the scheme and interchange fees on to the merchant, and adds a flat amount and/or a percentage per matching transaction |
Blended fee (blended_) | Ginger absorbs the scheme and interchange fees and charges the merchant one percentage, plus an optional flat amount, per matching transaction |
Recurring fee (recurring_) | A fixed amount every month or every payout, whatever the volume |
Chargeback tier fee (chargeback_) | A fixed amount per card scheme, chosen by the merchant's chargeback ratio of the past month |
Rolling reserve (rolling_) | A percentage held back for risk, released after a number of days |
IC++ or blended. Both apply to the transaction types and outcomes you choose: transaction types sale,
authorization, capture, refund, chargeback, void, aft and oct, outcomes
accepted and error. Each combination of transaction type and outcome uses either IC++ or blended pricing, not
both: a price plan that covers a combination twice is rejected.
Chargeback tier fees. After a month closes, Ginger measures the merchant's chargeback ratio for one card scheme: the amount of the merchant's closed disputes, lost or won, divided by the money that came in that month (sales, captures and account funding). The ratio falls in one band of the tier ladder, and that band's fixed fee is charged on the first payout of the next month. The bands:
- start at
0.00% and run back to back: each band includes its lower bound and excludes its upper bound; - the first band is always free (fee
0), so merchants without chargebacks pay nothing; - the last band has no upper bound (
to_ispercentage null).
Lost and won disputes both count, because the card schemes count every dispute, whatever its outcome. See the changelog entry of 8 September 2026.
Rolling reserve. A percentage of the money that came in on the payout (its sales, captures and account funding,
before fees and refunds) is held back for hold_ days, and then released in the first payout after that. The
Reserves tab of the configuration shows what is held and when it's released.
Adjustments
An adjustment adds money to, or takes money from, the next payout of a configuration: a positive amount credits the
merchant, a negative amount debits. An adjustment is pending until a payout picks it up, then applied. You can
delete a pending adjustment. Adjustments are in euros.
Set up payouts for a merchant
- Open the merchant and go to the Payout tab.
- Click Add configuration. The wizard asks for:
- Scope: Merchant-level or Project-level, and the project.
- Schedule: frequency, day, per-transaction delay, cutoff time and timezone.
- Bank account: account holder, IBAN, BIC and description. Or tick Skip for now.
- Price plan: add IC++ markups or blended fees, recurring fees, chargeback tier fees and a rolling reserve. You can add fees later.
- Check the Review step and click Create configuration.
The configuration page shows the next payout, the readiness checklist, and tabs for the schedule, bank account, price plan, adjustments and reserves.
Create a payout entity with its schedule, price plan and bank account in one request. Leave project_ out, or set
it to null, for a merchant-level configuration.
curl https://api.example.com/v1/admin/payouts/payout-entities/ \
--user "$API_KEY:" \
--header "Content-Type: application/json" \
--data '{
"merchant_id": "'"$MERCHANT_ID"'",
"payout_settings": {
"frequency": "weekly",
"day": 1,
"delay_days": 2,
"cutoff_time": "23:59",
"cutoff_timezone": "Europe/Amsterdam"
},
"price_plan": {
"fees": [
{
"type": "blended_fee",
"name": "Card payments",
"currency": "EUR",
"transaction_types": ["sale", "capture"],
"outcomes": ["accepted"],
"rate_percentage": "1.50",
"flat_amount": 10
}
]
},
"account_details": {
"account_holder": "Acme Coffee B.V.",
"iban": "NL00BANK1234567890",
"bic": "BANKNL2A"
}
}'See Create a payout entity in the API reference for every fee type, with an example of each.
Change a configuration later with separate calls: the schedule, the bank account, the price plan (send the complete list of fees) and the status. Add money to or take it from the next payout with an adjustment.
Fields on merchants and contracts
Some fields on merchants and contracts come from the payout and billing set-up before Ginger Payout:
- On the
credit-cardandbancontactcontracts,payout_ismodel collecting(your platform pays the merchant) ordistributing(the processor pays the merchant directly). The default isdistributing. - On the same contracts,
fee_says where the fees come from. Onlysource externalis accepted: the fees are imported from the processor. msc_is deprecated: the fee calculation now comes from the price plan or from the processor.calculation_ type - On the merchant,
priceplan_,id payout_(system grossornet),payout_andscheme invoice_.charge_ method
Related
- Board a merchant
- Payouts in the payment acceptance docs: what merchants see.
- Statuses