Skip to content

How Ginger works

The parts of a Ginger platform, who does what, how Ginger's terms map to acquiring terms, and how the money moves.

Ginger runs your payment platform: a platform instance of your own, under your domain, with your merchants on it. Your team operates it, your merchants accept payments on it, and Ginger connects it to the processors, payment methods and fraud prevention services you choose.

The parts of your platform

flowchart
PartWho uses itWhat for
Admin portalYour operations teamBoard merchants, set their permissions and contracts, follow payments, support merchants. See Tour the portals.
Platform APIsYour developersAutomate what the Admin portal does, build your own portals, search payments. See the API reference.
Merchant portalYour merchantsFollow orders, refund, create payment links, manage their projects, users and API keys.
Order API and hosted payment pageThe developers of your merchantsAccept payments with payment links, the hosted payment page, their own checkout or a plugin for their webshop. Documented in the payment acceptance docs, which you can send your merchants.
Processors and payment methodsConfigured by your team, per projectProcess the payments. See Payments.
3-D Secure and fraud preventionConfigured by your team, per projectAuthenticate and screen the payments. See Risk & compliance.

Ginger terms for payment professionals

Some Ginger terms differ from what you're used to in acquiring. Read this table before the rest of the docs.

Ginger termIn acquiring terms
Platform instanceYour own white-label gateway: your tenant of Ginger, under your domain.
MerchantThe legal entity you contract with. It holds the company details, the bank account, the payouts and the base permissions: the products it may use. See Merchant hierarchy.
ProjectOne point of sale of the merchant: a webshop, app or sales channel, with its own trade name (DBA), merchant category code (MCC), website, API key and webhook URL. Comparable to an outlet.
ContractNot the merchant agreement. A contract is the processing configuration of a project for one processor or payment method: MIDs, TIDs, acceptor or BIN keys, credentials, card brands, currencies and capture modes. See Processor contracts.
MIDThe merchant ID that identifies the merchant to a card scheme or processor.
BIN keyAt Silverflow: the reference to your acquiring BIN. Acquirers only.
OrderThe payment request of the merchant: amount, currency and description. Its status tells the merchant whether to deliver.
TransactionOne payment attempt on an order, with one payment method: the authorisation or sale. A capture, refund, void or chargeback is a linked order with its own transaction.
User and roleA login to a portal, and a named set of permissions. Your own staff are system users of the Admin portal.

Every status of a merchant, project, order and transaction is on Statuses. The other terms are in the glossary.

Who does what

Who boards the merchant at the processor and who owns scheme compliance depends on your setup: acquirers process on Silverflow, PayFacs and ISOs under the acquiring of a partner on Elavon, Rapyd, Shift4 or IPG. See Choose your setup.

one card payment

A card payment goes from the merchant to your Ginger platform, on to your processor and the card scheme, and the answer comes back the same way. The order goes from new to processing to completed.

TaskGingerYouYour processorYour merchant
Run, upgrade and secure the platform, the card vault and the payment pagesYes
Contract the merchantYes
Create the merchant at the processorAcquirers: Ginger boards it at SilverflowPayFacs and ISOs: your processor
Enter the processing details in the contractYes
Set up 3-D Secure rules and fraud preventionYes
Scheme complianceForwards the dataAcquirersPayFacs and ISOs: your processor, as acquirerSends the customer data
Integrate the checkoutYes, with the payment acceptance docs
Handle chargeback disputesYes
Support the merchantSupports youFirst line

Checking your merchants (KYC) is usually done by the acquirer (you, or your partner acquirer), not by Ginger. Ask your Ginger contact, your account manager at Ginger, which PCI DSS requirements are yours.

How the money moves

A card payment is authorised and captured through Ginger, then cleared and settled by the processor. Depending on the contract, either the processor pays the merchant, or your platform collects the funds and pays the merchant out with Ginger Payout, after fees and reserves. Ginger Payout handles payments through Silverflow, in euros. See Money flow and settlement.

How you stay up to date

Ginger deploys the platform several times a day, to every platform instance at once. You don't install upgrades. The changelog lists every change, with an RSS feed for your team.

Next steps

Choose your setup: acquirer on Silverflow, or PayFac or ISO.