What Is an OCT (Original Credit Transaction)? The Definitive Guide to Push-to-Card Payments

For decades, card payments moved in one direction: from the cardholder to the merchant. You swiped, dipped, or tapped your card, and money flowed from your account to the business. But a fundamental shift has been underway. Businesses now need to send money to cards—not just collect money from them. Original Credit Transactions (OCTs) make this possible, and they are rapidly becoming the backbone of instant payouts across the global economy.

Whether you are building a gig economy platform that pays drivers in real time, an insurance company that settles claims within minutes, a lending platform that disburses loan proceeds to a borrower's debit card, or a money transfer operator that delivers remittances to recipients worldwide, OCTs are the mechanism that makes push-to-card payments work.

This guide is the most comprehensive OCT resource available. It covers everything from the basic definition and step-by-step transaction flow to compliance requirements, cross-border considerations, and a head-to-head comparison of every major payout rail. If you need to understand how OCTs work, when to use them, and how to implement them, start here.

What Is an Original Credit Transaction (OCT)?

An Original Credit Transaction (OCT) is a card network transaction that pushes funds directly to a recipient's debit card, prepaid card, or in some cases credit card. Unlike a standard purchase where money is pulled from the cardholder, an OCT moves money in the opposite direction—from a business or platform to the cardholder. The recipient sees the funds appear in their account, often within minutes.

The term "original credit" means that the transaction originates a credit to the cardholder's account without a prior corresponding debit. It is not a refund. It is not a chargeback reversal. It is a net-new credit—new money flowing to the card. This is what distinguishes an OCT from other credit transactions in the card network ecosystem.

Key Terminology

• Push payment – A payment initiated by the sender that pushes funds to the recipient. OCTs are push payments. The recipient does not need to initiate or authorize anything.
• Pull payment – A payment where funds are pulled from the payer's account, typically requiring the payer's authorization. Standard card purchases and Account Funding Transactions (AFTs) are pull payments.
• Push to card – The industry shorthand for using OCTs to send money to a card. Also referred to as "card payouts" or "instant payouts to debit card."
• Fast Funds – Visa's designation for OCT transactions that are delivered to the recipient within 30 minutes when the issuing bank supports real-time posting. Not all issuers support Fast Funds—some may take up to two business days.
• Card payout – A disbursement made to a payment card rather than a bank account. OCTs are the primary mechanism for card payouts on Visa and Mastercard networks.
• Originator – The business, platform, or entity that initiates the OCT and sends the funds. This is the sender.
• Recipient – The cardholder who receives the funds on their debit or prepaid card.

In practical terms, an OCT allows any business with a relationship to a card network processor to send money directly to a card number. The recipient does not need to share their bank account details, routing numbers, or IBAN. They only need a card—and billions of people around the world already have one.

How OCTs Work: Step-by-Step

Understanding the OCT transaction flow is essential for any business considering push-to-card payments. While the end result appears simple—money shows up on a card—the underlying process involves multiple parties and distinct phases.

Fast Funds: The Speed Advantage

The speed at which the recipient sees funds depends on their issuing bank. Visa Direct's Fast Funds program enables delivery within 30 minutes for eligible issuers. Visa maintains a lookup service that allows originators to check whether a specific card is eligible for Fast Funds before initiating the OCT. This is important for use cases where speed is critical—gig worker payouts, emergency insurance claims, or time-sensitive money transfers.

When Fast Funds is not available, the OCT still works, but the recipient may not see the credit for up to two business days. For many use cases, this is still significantly faster than ACH or wire transfer alternatives.

OCT vs AFT: The Pull-Push Pair

OCTs and AFTs (Account Funding Transactions) are two sides of the same coin. They are designed to work together as a complementary pair within the card network ecosystem.

The AFT-OCT Flow in Money Transfers

The classic example of AFTs and OCTs working together is the person-to-person money transfer. Here is how the flow works end-to-end:

1. Sender initiates a transfer – The sender wants to send $200 to a family member. They provide their own debit card and the recipient's card number.
2. AFT pulls funds from the sender – An Account Funding Transaction debits $200 from the sender's card. The money transfer platform now holds the funds.
3. Platform processes the transfer – The platform performs compliance checks (KYC, AML, sanctions screening), calculates any fees or currency conversion, and prepares the payout.
4. OCT pushes funds to the recipient – An Original Credit Transaction credits the recipient's debit card with the payout amount. The recipient sees the funds appear in their account.

This AFT-OCT pair is the foundation of card-based money movement. It enables platforms to collect funds using a card (AFT) and disburse funds to a card (OCT) without ever touching bank account details, routing numbers, or IBAN codes. The entire flow runs on card rails, which means it works anywhere Visa and Mastercard are accepted—across more than 200 countries and territories.

For a deeper understanding of the collection side, see our complete guide to Account Funding Transactions (AFTs). For businesses that need to collect AFTs remotely, payment links built for AFT programs enable SMS and WhatsApp-based fund collection.

Visa Direct and Mastercard Send: The Networks Behind OCT

OCTs do not exist in a vacuum. They are delivered through the real-time payment capabilities built on top of the two dominant card networks. Visa's offering is called Visa Direct. Mastercard's offering is called Mastercard Send. Both enable push-to-card payments using OCTs, but they differ in important ways.

Visa Direct

Visa Direct is Visa's real-time push payments platform. It enables businesses to send funds to Visa debit cards, prepaid cards, and (in certain cases) credit cards globally. Visa Direct leverages the existing VisaNet infrastructure, which means it can reach any Visa card in the world—an enormous distribution advantage.

Key characteristics of Visa Direct:

• Fast Funds: Eligible transactions are delivered within 30 minutes to issuers that support real-time posting
• Global reach: Available in over 200 countries and territories through the VisaNet network
• Card eligibility API: Allows originators to check whether a specific card supports OCTs and Fast Funds before sending
• Transaction limits: US domestic P2P default limit of $2,500 per transaction, with exceptions up to $10,000 based on program type and risk controls
• Velocity controls: Rolling limits enforced across 1-day, 7-day, and 30-day periods to prevent abuse
• Multi-currency: Supports cross-border OCTs with network-level currency conversion

Mastercard Send

Mastercard Send is Mastercard's equivalent push payment service. It enables OCTs to Mastercard debit and prepaid cards through the Banknet network. Like Visa Direct, it aims to deliver funds quickly, though the exact speed depends on the receiving issuer's capabilities.

Key characteristics of Mastercard Send:

• Speed: Funds are available within minutes for participating issuers, with a broader settlement window for others
• Global reach: Available across the Mastercard network in more than 150 countries
• Payment types: Supports person-to-person (P2P), business-to-consumer (B2C), and government-to-consumer (G2C) use cases
• Mastercard Payment Gateway Services: Provides processing infrastructure for acquirers and processors connecting to Mastercard Send
• Cross-border capability: Supports international OCTs with multi-currency settlement

Visa Direct vs Mastercard Send: Head-to-Head

For businesses that need to reach the broadest possible recipient base, supporting both Visa Direct and Mastercard Send is essential. A recipient may hold a Visa debit card, a Mastercard prepaid card, or both. A payment orchestration platform that routes OCTs to the correct network based on the recipient's card BIN ensures maximum coverage and optimal delivery speed.

OCT Use Cases by Industry

Original Credit Transactions are not limited to a single industry or use case. Any business that needs to send money to individuals can potentially use OCTs. Here are the most significant use cases across the global economy.

Gig Economy and Marketplace Payouts

Rideshare drivers, food delivery couriers, freelance workers, and marketplace sellers increasingly expect instant access to their earnings. OCTs enable platforms to push daily (or even per-job) earnings directly to a worker's debit card within minutes, eliminating the traditional wait of one to five business days for ACH settlement. For gig workers who depend on immediate cash flow, instant payouts via OCT are not a nice-to-have—they are a competitive differentiator that affects driver recruitment and retention.

Insurance Claims Disbursement

When a policyholder files a claim—whether for auto damage, health expenses, or property loss—the traditional disbursement process involves mailing a check or initiating an ACH transfer that takes days to settle. OCTs allow insurers to push approved claim payments directly to the policyholder's debit card within minutes. This dramatically improves the customer experience during what is often a stressful time, and it reduces operational costs associated with check printing, mailing, and handling.

Lending and Loan Disbursement

Online lenders, buy-now-pay-later platforms, and microfinance institutions can use OCTs to disburse approved loan proceeds directly to the borrower's debit card. Instead of waiting for an ACH credit to clear, the borrower has access to funds within minutes of approval. For short-term lending products where speed is a core value proposition, OCT disbursement is particularly compelling.

E-Commerce Returns and Refunds

While standard card refunds (reversals) exist, they can take 5–10 business days to appear on a cardholder's statement. OCTs offer an alternative path for e-commerce platforms that want to deliver instant refunds. Rather than processing a refund through the original transaction's reversal flow, the platform can initiate an OCT to credit the customer's card immediately. This is especially useful for high-volume marketplaces where customer satisfaction and return-to-purchase conversion rates are critical.

Online Gaming and Gambling Winnings

When a player wins money on a regulated gaming or gambling platform, they want their winnings fast. OCTs enable platforms to push payouts to the player's debit card within minutes, rather than requiring a bank transfer or check. This speed improves the user experience and reduces support tickets from players asking "where is my money?"

Government Disbursements

Government agencies at the federal, state, and local level distribute billions in benefits, tax refunds, disaster relief payments, and stimulus payments. OCTs offer a fast, card-based disbursement channel that can reach recipients who may not have a traditional bank account but do have a prepaid debit card. This is a significant advantage for unbanked and underbanked populations.

Earned Wage Access (EWA)

Earned wage access platforms allow employees to access a portion of their earned but unpaid wages before their scheduled payday. OCTs are the disbursement mechanism: when an employee requests an early wage draw, the EWA platform pushes the requested amount to their debit card via OCT. The platform later collects the corresponding amount from the employer during the normal payroll cycle. Speed is everything in EWA—employees requesting early wage access typically need the funds that day, not in two to three business days.

Money Transfers and Remittances

This is the original use case for OCTs in the context of cross-border payments. A sender funds a transfer (often via AFT or payment link), and the recipient receives the payout on their debit card via OCT. For remittance corridors where recipients have debit or prepaid cards, OCTs offer a faster and more convenient alternative to cash pickup, bank deposit, or mobile money.

OCT for Domestic Payouts: How It Compares to Every Other Rail

When a business needs to send money domestically in the United States, OCTs are just one of several available payout rails. Each rail has different speed, cost, coverage, and limit characteristics. The following comparison table provides a neutral, side-by-side analysis of the five primary domestic payout methods.

When to Choose OCT Over Other Rails

OCTs excel in specific scenarios that other rails struggle with:

• You only have the recipient's card number. ACH, RTP, and FedNow all require a bank account and routing number. OCTs require only a card PAN. For consumer-facing payouts where collecting bank details adds friction, this is a major advantage.
• You need speed and cross-border reach in the same transaction. ACH, RTP, and FedNow are domestic-only. Wire transfers are global but slow and expensive. OCTs via Visa Direct and Mastercard Send offer near-instant delivery across 200+ countries.
• Your recipients are unbanked or underbanked. Prepaid debit cards are available to people without traditional bank accounts. OCTs can reach prepaid cards, making them an inclusive payout option for populations that would otherwise be excluded from electronic disbursements.
• You need 24/7/365 availability. ACH and wire transfers are limited to banking hours and business days. OCTs (and RTP/FedNow) operate around the clock. For platforms that process payouts on weekends, holidays, and after hours, card rails are always available.

When Not to Choose OCT

• High-value payouts. OCT per-transaction limits (default $2,500 for P2P) make them unsuitable for large business-to-business payments or high-value settlements. Wire transfers or ACH are better for these.
• Bulk batch payouts at lowest cost. ACH remains the most cost-effective rail for high-volume, non-urgent domestic payouts where speed is not critical.
• Payouts to business bank accounts. OCTs target individual cards. For B2B payouts to commercial bank accounts, ACH, wire, or RTP are more appropriate.

OCT for Cross-Border Payouts

One of the most powerful advantages of OCTs is their inherent cross-border capability. Because OCTs travel on Visa and Mastercard networks—which are global by design—a single integration can reach recipients in over 200 countries and territories. This is a fundamentally different proposition from domestic-only rails like ACH, RTP, and FedNow.

Currency Conversion

Cross-border OCTs typically involve currency conversion. If an originator in the United States sends a payout to a recipient in Mexico, the funds must be converted from USD to MXN. There are two primary approaches:

• Network FX – The card network (Visa or Mastercard) performs the currency conversion at the network exchange rate. This is the simplest approach and is built into the OCT flow. The originator sends in their local currency, and the recipient receives in their local currency.
• Originator FX – The originator (or their processor) handles the currency conversion before submitting the OCT. The OCT is submitted in the recipient's local currency. This approach gives the originator more control over exchange rates and margins but requires the originator to manage FX risk and have access to the destination currency.

The choice between network FX and originator FX depends on volume, corridor, margin requirements, and the originator's treasury capabilities. High-volume remittance corridors often benefit from originator FX with negotiated rates, while lower-volume or long-tail corridors may be more efficiently served by network FX.

Corridor Availability

Not every country and every issuer supports inbound OCTs equally. While Visa Direct and Mastercard Send have broad global reach, the actual availability of push-to-card payouts depends on:

• Issuer participation: The recipient's issuing bank must support inbound OCTs. Most major issuers do, but smaller or regional banks may not.
• Regulatory restrictions: Some countries restrict or regulate inbound cross-border card credits. Compliance with local regulations is mandatory.
• Card type: Debit and prepaid cards are broadly supported. Credit card OCTs are more restricted and depend on the issuer's policy.
• Sanctions and embargoes: Certain countries or entities are prohibited from receiving funds under US (OFAC), EU, or other sanctions regimes.

Before deploying cross-border OCTs in a new corridor, originators should use the card network's eligibility APIs to verify that the destination cards support inbound OCTs and, ideally, Fast Funds or equivalent real-time posting.

Cross-Border Compliance

Cross-border OCTs are subject to regulatory requirements in both the originating and receiving countries. Key compliance considerations include:

• KYC on both ends: The originator must verify the identity of the sender. In many corridors, the receiving side also requires identity verification of the recipient.
• AML transaction monitoring: Cross-border card payouts must be monitored for patterns consistent with money laundering, structuring, or terrorist financing.
• Sanctions screening: Every cross-border OCT must be screened against OFAC (US), EU, UN, and other applicable sanctions lists before funds are released.
• Reporting obligations: Certain corridors and amounts trigger reporting requirements under the Bank Secrecy Act (BSA) and equivalent regulations in other jurisdictions.
• Transfer of Funds Regulation (EU): OCTs to recipients in the EU/EEA must include originator and beneficiary information as required by the Transfer of Funds Regulation.

OCT Compliance and Risk Management

Operating an OCT program is not simply a matter of technical integration. Card networks, regulators, and acquiring banks all impose compliance requirements that OCT originators must meet. Failing to comply can result in transaction declines, network fines, program suspension, or regulatory action.

KYC and AML Requirements

Every OCT program must have robust Know Your Customer (KYC) and Anti-Money Laundering (AML) controls. At a minimum, this includes:

Sanctions Screening

Every OCT must be screened against applicable sanctions lists before the transaction is submitted to the card network. In the United States, this means OFAC's Specially Designated Nationals (SDN) list at a minimum, plus any other applicable lists (EU, UN, HMRC, etc.) depending on the corridors served. Sanctions screening must cover the sender, the recipient, and any intermediary entities.

Transaction Limits and Velocity Controls

Card networks enforce transaction limits and velocity controls on OCT programs to manage risk. These controls operate at multiple levels:

• Per-transaction limits: Visa Direct enforces a default US domestic P2P limit of $2,500 per transaction, with exceptions up to $10,000 for approved programs. Mastercard Send limits vary by program type and issuer.
• Velocity limits: Visa enforces rolling limits across 1-day, 7-day, and 30-day periods. These limits cap the total OCT volume that can be sent to a single card or from a single originator within each rolling window.
• Program-level limits: The acquiring bank or processor may impose additional limits based on the originator's risk profile, program type, and compliance history.
• Issuer-level limits: The receiving issuer may decline OCTs that exceed their own inbound credit limits for a given card or account.

Visa Reason Code 13.8 – Original Credit Transaction Disputes

While OCTs are not traditional purchases and cannot be disputed in the same way a cardholder disputes a purchase, there is a specific Visa dispute reason code that applies: Reason Code 13.8. This code covers situations where a cardholder claims they did not authorize or recognize an OCT credit to their account. While less common than purchase disputes, originators must be prepared to respond to 13.8 disputes by providing documentation of the transaction, including the sender's identity, the purpose of the OCT, and evidence that the correct card was credited.

Maintaining clean records, robust KYC documentation, and clear transaction descriptions minimizes the risk and impact of OCT disputes.

How to Get Started with OCTs

Implementing an OCT program requires selecting the right partners, integrating with the appropriate infrastructure, and building the compliance framework to operate safely. Here is what the process looks like.

Choosing a Processor

OCTs are not something a business submits directly to Visa or Mastercard. You need a processor (also called an acquirer or a program manager) that has a direct connection to the card networks and is approved to originate OCTs on your behalf. When evaluating processors, consider:

Integration Approaches

There are three primary approaches to integrating OCT capabilities into your platform:

1. Direct API integration – You integrate directly with your processor's OCT API. This gives you the most control over the user experience and transaction flow but requires significant engineering investment. You are responsible for building the payout logic, error handling, retry mechanisms, compliance screening, and reconciliation.
2. Payment orchestration platform – You integrate with a payment orchestration platform that connects to multiple processors and card networks behind a single API. The orchestrator handles network routing, failover, compliance, and reconciliation. This approach reduces engineering complexity and provides flexibility to add new processors or corridors without rebuilding your integration.
3. Embedded payout widget – Some processors offer pre-built UI components or hosted payout pages that you embed in your application. The processor handles the card input, validation, and OCT submission. This is the fastest path to launch but offers the least control over the user experience.

For businesses that are scaling across multiple use cases, corridors, and card networks, the payment orchestration approach offers the best balance of speed, flexibility, and control. A single integration connects you to Visa Direct, Mastercard Send, and other payout rails, with intelligent routing that optimizes for speed, cost, and success rate.