Push-to-card payouts, explained

What is push-to-card?

Push to card is a way to pay someone using nothing but their debit card number. In plain words, that is what push-to-card means: the sender pushes money onto the card instead of pulling a payment off it the way a purchase does, and the funds end up in the bank account behind the card. The recipient never shares routing and account numbers. They share the card in their wallet, which is often the one payment detail they actually know.

How push-to-card payouts work

Card networks were built to move money in both directions. A push-to-card payout is an OCT-style credit, short for original credit transaction: the payout platform sends a credit over the card network to an eligible debit card, and the card’s issuing bank deposits the money into the bank account behind that card. When the issuing bank supports fast funds, the money is typically available in about a minute. DiscoFi’s push-to-card rail is Visa Direct.

Business
   |
Payout platform
   |
Visa Direct (OCT credit)
   |
Eligible debit card
   |
Recipient's bank account

Eligibility is the main constraint. Push-to-card works for debit cards from banks that support fast funds. Some prepaid cards and most credit cards are not eligible, which is why platforms check a card before routing money to it.

Push-to-card vs push-to-account

The other family of payout rails is push to account: sending money straight to a bank account over a bank transfer rail. That covers RTP and FedNow on the instant side and ACH on the batch side. The practical difference is what the recipient has to give you. Push to account needs routing and account numbers; push to card needs a debit card number. Bank rails are usually cheaper per payout, while push-to-card is easier for the recipient. The cost and timing tradeoffs across ACH and the instant rails are their own topic, but the short version is that no single rail wins every payout.

Push-to-card vs RTP and FedNow

RTP, FedNow, and push-to-card can all land money in about a minute when the recipient’s bank supports the rail. The difference is coverage. RTP and FedNow only reach recipients whose banks have joined those networks, and RTP and FedNow cover different sets of banks. Debit card coverage is much broader: nearly every adult with a bank account carries one. So bank instant rails tend to win on cost when they are available, and push-to-card wins when they are not, or when the recipient would rather hand over a card number than bank details.

Push-to-card for incentives and rewards

Incentive and reward payouts are where push-to-card earns its keep. Research incentives, referral bonuses, contest winnings, promotional rewards: these programs pay one-off recipients who have no ongoing relationship with the payer. Asking a one-time recipient to dig up routing and account numbers is where those programs stall. A debit card number is often the only detail a recipient is comfortable sharing, and for many it is the only detail they can produce on the spot. Push-to-card lets the reward arrive minutes after the recipient shares that card number, which is the whole point of an incentive.

How a push-to-card API fits into a payout platform

Few programs should run on push-to-card alone, because few should run on any single rail. In a payout platform, push-to-card is one option the router weighs per payout: try the fastest rail the recipient can accept, and fall back if it is unavailable or the card is ineligible. DiscoFi routes each payout across RTP, FedNow, Visa Direct, and ACH, and on instant rails funds typically land in about a minute when the recipient’s bank supports the rail.* See Instant Pay disclosure If a recipient shares a debit card instead of bank details, the payout still goes out in the same batch, through the same payout API, with live status either way. To see which rail a given payout would take, try the rail selector. Push-to-card is not priced as its own product: DiscoFi’s pricing is one rate on successful payout volume, however the money gets there.