Glossary

Term	Definition
Access token	The OAuth 2.0 bearer token you obtain with your client credentials and send on every API call. Valid for 24 hours.
Arc	Green Dot's embedded finance platform. Digital Money Movement is a capability of Arc.
BaaS	Banking-as-a-Service. The documentation set for partners whose recipients need an account at Green Dot Bank.
Business logic	Your application's rules that decide who is paid, how much, and when. Green Dot executes payouts; it does not perform business logic.
Card link	The stored association between a recipient profile and one of their debit cards, created in the Standard Disbursements Flow. A recipient can have more than one.
Card link ID	The identifier of a card link (`link.linkId`). Used as the destination identifier when sending a payout to that card.
Customer profile	The API object representing a recipient in the Standard Disbursements Flow. Identified by a `customerToken`.
Customer token	The identifier of a customer profile (`customerToken`). Used in the path when linking a card and when retrieving that recipient's transfers.
Debit Push	The Digital Money Movement payout method: funds sent over the card networks to the account behind a recipient's debit card, in near real-time. Sometimes referred to as an instant disbursement.
Disbursement	The outbound transfer of funds from your organization to a recipient.
Disbursement business account	Your funded business account at Green Dot Bank that payouts are pushed from. Identified by the disbursement account identifier issued at onboarding.
Payee site identifier	The destination identifier used in the Single Call Disbursement Flow (Async). Issued at onboarding.
PCI	Payment Card Industry standards governing how debit card data must be handled.
PCI widget	Green Dot's hosted card capture interface. Collects card details directly so they never pass through your systems.
Program code	The short code identifying your program. Appears as `{programCode}` in most request paths.
Recipient	The person who receives a payout. Represented in the API as a customer profile in the Standard Disbursements Flow.
Single Call Disbursement Flow (Async)	The debit push integration where recipient details, card details, and amount travel in one request and the outcome arrives by webhook. Nothing is stored for reuse.
Standard Disbursements Flow	The debit push integration where you create a recipient profile, link their card, and then send transfers to the stored card. Responses are synchronous.
Transfer identifier	The GUID you generate to identify a payout. Your idempotency key — reuse it on retries, never across payouts.
Webhook	An HTTP callback Green Dot sends to an endpoint you host when a payout reaches a final state. Used by the Single Call Disbursement Flow (Async).

A note on terminology

Disbursement and payout both refer to the outbound money movement from your organization
to a recipient, and are used interchangeably. The word transfer appears where it is a literal API
field name or path segment — transferIdentifier, POST /transfers — because that is what the API
calls it.

Similarly, the API uses customer for the person being paid, while this documentation uses
recipient in prose. They refer to the same person.

Updated about 23 hours ago

Did this page help you?