Platform Features
Platform Features
Digital Money Movement delivers payouts through Debit Push: funds sent over the card networks
to the account behind a recipient's debit card, in near real-time.
Debit Push
A Debit Push payout sends funds from your disbursement business account directly to the account
linked to the recipient's debit card. Funds typically arrive in near real-time, and payouts work
24/7, including outside banking hours.
| Attribute | Detail |
|---|---|
| What it is | Funds pushed over the card networks to the account behind a debit card |
| Speed | Near real-time, 24/7 |
| Source of funds | Your disbursement business account at Green Dot Bank |
| Recipient needs | An eligible debit card |
| Supported currency | USD |
When it fits
Debit Push fits any payout where the recipient holds a debit card and receiving funds quickly
matters: earned wages, claim proceeds, seller settlements, refunds. Because it involves card data,
that data must be handled in line with PCI requirements — collected, transmitted, and stored only
through compliant channels.
Card eligibility
The recipient must have an eligible debit card. Certain card types are not accepted, including some
prepaid programs, credit cards, and cards on unsupported networks.
Green Dot checks eligibility for you:
- When a card is linked in the Standard Disbursements Flow, Green Dot verifies that the card's
BIN is eligible for fast-funds push payments through the card networks. - Before a transfer executes, in either flow, Green Dot validates the card again and returns
an error for ineligible card types.
When a payout is declined for card eligibility, ask the recipient for a different debit card rather
than retrying the same one. See Response Codes.
Keeping card data out of your systems
Card data is the most sensitive thing in this flow. Green Dot gives you two ways to keep your PCI
scope small:
- Hosted PCI widget. A secure, Green Dot–hosted interface that captures the recipient's card
details directly. The card number never touches your servers. - Field-level encryption. If you collect card details yourself, they must be encrypted with
your program's public certificate before transmission. See
Encrypting sensitive data.
Either way, card numbers are never sent to Green Dot in plain text.
Two ways to integrate
Debit Push is available through two integration flows. Both deliver the same payout to the same
kind of card; they differ in whether Green Dot stores the recipient and card for reuse, and in how
you receive the result.
| Standard Disbursements Flow | Single Call Disbursement Flow (Async) | |
|---|---|---|
| How it works | Create a recipient profile and link their card once, then send transfers against the stored card | Send recipient details, card details, and amount together in one request |
| API calls for the first payout | Three | One |
| API calls for later payouts to the same person | One | One, with full details resubmitted |
| Recipient and card stored at Green Dot | Yes | No |
| How you receive the outcome | Synchronously, in the transfer response | Asynchronously, by webhook |
| Tends to suit | Programs that pay the same recipients repeatedly | Programs that pay each recipient once or occasionally |
Neither flow is the default. Choose based on how your program pays people, and use both if your
program has both patterns. See
Choosing an integration flow.
| To do this | Read |
|---|---|
| Integrate the Standard Disbursements Flow | Standard Disbursements Flow |
| Integrate the Single Call Disbursement Flow (Async) | Single Call Disbursements Flow (Async) |
Updated about 23 hours ago
