Skip to content

Glossary

The terms of the Ginger platform, its portals, its connectors and these docs.

The terms used on the platform and in these docs, grouped by topic. Each links to the page that explains it.

Platform

TermMeaning
Admin portalThe portal of your team: boarding, permissions, contracts, support. See Tour the portals.
Base permissionsThe most a merchant may ever do, set only by you. Its projects, users and roles stay within them. See Merchant hierarchy.
ContractThe configuration of a processor or payment method for a project: merchant IDs, credentials, currencies, capture mode. See Processor contracts.
MerchantA business you contract with. It has projects, users and roles.
Merchant portalThe portal of your merchants: orders, refunds, payment links, their own projects and users.
Merchant tagA label on a merchant, copied to its orders and transactions. See Merchant tags.
Platform instanceYour own Ginger platform, under your domain.
ProjectOne place where a merchant accepts payments, with its own API key, webhook URL, payment methods and contracts.
RoleA named set of permissions, given to users.
System userA user of your own team, in the Admin portal.
Test modeA project with the status active-testing: its orders get the is-test flag and go to the test environments of the connectors. See Take a test payment.
UserA login to a portal. A merchant user sees one merchant.

Payments

TermMeaning
Capture modeWhether a card payment is captured at once or authorised first and captured later. See Processor contracts.
FlagsA summary of the history of an order, such as is-test or has-refunds. See Statuses.
Hosted payment pageThe payment page Ginger shows when a merchant redirects its customer. See Style the hosted payment page.
OrderWhat a customer pays for: an amount, a currency and a description. Its status tells the merchant whether to deliver.
TransactionOne payment attempt for an order, with one payment method.

Every status of a merchant, project, order and transaction is on Statuses.

Card processing

TermMeaning
Acceptor keyThe Silverflow acceptor of a project for one card scheme, mac-…. See Merchant boarding.
AFTAccount Funding Transaction: a payment that pulls money from a card to fund another account. See Account Funding Transactions.
AReqThe authentication request of 3-D Secure. Mastercard sets which customer data it holds. See Mastercard 3DS AReq data.
BEPThe protocol of Bancontact app payments. See Bancontact.
BIN keyThe reference to your BIN at Silverflow, bin-….
Boarding modeHow Ginger boards a project at Silverflow: full-merchant, acceptors-only or disabled. See Merchant boarding.
EndeavourThe 3-D Secure server used for Elavon. See Elavon.
Funding chargeThe Silverflow charge type of an AFT.
Low value exemptionSkipping 3-D Secure for payments under a threshold.
Merchant keyThe Silverflow merchant, mct-….
MIDMerchant ID: the merchant at the processor, often one per card brand.
Network transaction IDThe reference of the card scheme, used for recurring payments.
OCTOriginal Credit Transaction: a payout to a card.
PARPayment Account Reference: one reference for a card account across its card numbers and tokens.
Settlement IDThe transaction reference in the Elavon settlement file. See Settlement IDs.
Soft declineA decline in which the issuer asks for 3-D Secure; the payment is retried with it.
TIDTerminal ID, at the processor.
TLIDMastercard's Transaction Link ID, linking the transactions of one payment.

Fraud prevention

TermMeaning
Fraud ruleA block on payments of a project by BIN, BIN country, country, IP address or card. See Ginger fraud rules.
Report-only modeThe fraud provider decides, but Ginger never declines on its decision. See Fraud prevention.
Risk profileThe profile of the fraud provider that sets how strict its decision is, per project.

APIs

TermMeaning
Admin API keyThe API key of a project in your admin merchant, with permission on the platform APIs. See API keys.
Field permissionA read or write limit on a field of a project, for users. See Permissions.
JWKSA published set of public keys, to verify signatures. See Gateway order API.
JWSA signature of the body of a request or response.
Path permissionAn API path pattern with the HTTP methods allowed on it. See Permissions.
Project API keyThe API key of a project, sent as the username of HTTP Basic authentication with an empty password.
search_afterThe cursor to page through search results. See Search API.
selfA placeholder in a path for the merchant, project or user of the caller.
Stream pointerThe last sequence number your system processed from the Stream API.
TokenThe temporary credential of a logged-in user. See Log in with a username and password.
Trusted tokenA token that lets a device skip multi-factor authentication for a while.