Overview of Instant Pull Payments
Accept single and recurring payments.
New to TabaPay? Start Here
1. Learn
If you are just learning about TabaPay you can begin at Getting Started, and About TabaPay.
2. Chat
To make your first API call, you will first need access to Sandbox. Talk to sales to discuss your use case or get help at [email protected].
3. Test
Once you have access to sandbox from TabaPay Support, look at some code samples with recipes or feel free to post your questions in the developer forum.
Payload Should Be CompactEach API request body should be formatted in compact JSON when sending a request to the TabaPay API.
Note: If you don’t have access to Sandbox, please reach out to [email protected] .
Accept single or recurring payments instantly. Move funds instantly from your customer's card or bank account to your destination account. Get Started with Pull Payments →
- Fund a newly opened account, topping up a wallet’s stored value, or enabling recurring or one-time payments. See Code Samples →
For more information, take a look at our webinar.
Definition: AFT
An instant pull can be an Account Funding Transaction (AFT), or a Purchase transaction.
- Account Funding Transaction (AFT): A financial transaction that withdraws funds from a cardholder's account to fund another account, card or non-card. AFTs are often account to account (A2A) transactions.
Note: AFTs may also be used in conjunction with an instant push or original credit transactions (OCTs).
- Purchase transaction: A financial transaction that debits a cardholder's account.
Use Cases
Debt Repayment
Subscription Funding
General eCommerce
Account FundingWhy Choose Pull Payments at TabaPay?
-
Flexible Funding Sources: Fund accounts using a customer card or bank account.
-
Stronger Risk Controls: Incorporate payment card verification methods to help reduct fraud and improve authorization rates. Use tools like AVS, ANI, and Duplicate checks.
-
Built in Compliance: Incorporate compliance tools in your workflow including OFAC screening, 3DS authentication, Real-time monitoring.
-
Tokenization: Support for device tokens such as Apple Pay, Google Pay, e-Commerce or Card on File tokens, as well as Processor Tokens. For a PCI-compliant way to handle payment cards refer to TabaPay Tokens.
Instant Pulls vs Instant Pushes
Instant pulls, or Account Funding Transactions (AFT) are payment acceptance transactions.
Instant pushes, or Original Credit Transactions (OCT)/Payment Transactions are payouts.
Instant pulls and instant pushes may be used as either separate, stand-alone transactions, or they can be linked as part of one overall funds transfer transaction.
Transaction Types
Refer to the table for different types of transactions including Account Funding Transactions AFT, Quasi-Cash and purchase transactions. Each has different correlating use cases.
Type of Transaction | Description | Use Cases |
|---|---|---|
Account Funding | Account funding from a supported funding source with our TabaPay Unified API with the intent of funding a non-merchant account. |
|
Quasi-Cash | Account funding for the purchase of an item that is representative of actual cash or a substitution for cash. |
|
Purchase Transaction | Paying a merchant for goods or services |
|
Domestic vs International
- When the acquirer and the issuer are in the same country, it is considered Domestic.
- When the acquirer and the issuer are in different countries, it is considered International.
Pull Transaction Payment Flow
This high-level simplified payment flow applies to both AFTs and general purchase transactions.
- Customer initiates transaction on your platform/website.
- You send the Create Transaction API with
type:pull - TabaPay sends the transaction request to the card network.
- Network returns with the approved amount.
- TabaPay sends Create Transaction response.
- You present the approved transaction to the customer.
Pull Payment Features
Partial Auth
Authorize & Capture
Apple Pay
Google Pay
Level 2 and Level 3 DataHow Instant Pull Payments Work
Prerequisites
Fraud Checks
Before collecting payment data you could initiate optional fraud checks on a card and the cardholder using AVS ,ANI, CVV2, and Duplicate Card Checks.
OFAC screening may be highly recommended for some use cases and international payments. Check if the individual initiating the transaction is compliant with OFAC before you initiate the payment request.
Collect Payment Source Data
Request your customer to enter a payment source. For example, you may collect information using the
Browser SDK, or collect through your own API payment flow if you are PCI compliant.
Create Account
Safely store the payment data with TabaPay so you do not have to worry about handling PII and meeting PCI standards.
Note: This will generate an accountID and will eventually populate the Source Account ID information.
Check Eligibility of Payment Source
If this source account is a payment card, you would first check to see if it is eligible for a pull transaction (i.e. is the card eligible for type:pull?).
1. Create Transaction Request
Proceed with the request to initiate the transaction for the required amount and request body parameters based on the use case.
2. Create Transaction Response
Receive the response immediately via API with the return code in the response.
Recommendations
If you do not want to deal with storing of sensitive information or handling payment cards in a compliant manner, and would rather TabaPay do the heavy-lifting for you, utilize our internal TabaPay Token vault to securely retrieve a TabaPay Token (Account ID) for your payment cards using our Create Account API. Learn more about TabaPay Tokens →
Code Samples to Accept Payments
A few samples to get you started!
Updated 3 days ago