Account Funding for Neobanks
🏁 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 Compact
Each 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] .
Account Funding for Neobanks is a general use case where money is pulled into accounts that have been opened for any Neobank or fintech consumer account.
TabaPay's payment methods and features provide flexible solutions for your customers to fund their accounts. Utilize TabaPay's extensive network of cards, bank payments, and wallets to streamline account funding. You can accept and securely gather customer information using the Dynamic iFrame, or if you have a preexisting PCI compliant payment flow, you can integrate solely with the TabaPay API.
Use Cases
- Consumer Accounts: Enable users to fund their savings or spending accounts instantly using cards, ACH, or digital wallets.
- Business Banking: Simplify deposits for freelancers, startups, or small businesses, ensuring easy access to working capital.
- Person-to-Person (P2P) Transfers: Facilitate quick and secure funding for users to send and receive money within neobank accounts.
Account Funding Create Transaction Flow
- Customer opens an account on your platform—follows your flow to deposit funds.
- You send the Create Transaction Request with
type:pull. - TabaPay sends the transaction request to the card network.
- Network returns with an approved amount of $100.
- TabaPay sends Create Transaction response.
- You present the approved payment to the customer.
Payment Options
Card
Bank
WalletPayment Features
You can use different payment features to implementing for your Account Funding use case.
Feature Enablement at TabaPay
- TabaPay clients who wish to integrate with your use case must work with their TabaPay representative to select features.
- You can request Partial Authorization for your use case.
- No enablement is required for cardholder-initiated vs merchant-initiated transactions.
Payment Features to Consider
| Payment Feature | Benefit | Recommendation | CIT | MIT |
|---|---|---|---|---|
| Partial Authorization Service | While prepaid and debit cards are used for instant pull payments, what happens if they do not have enough funds to cover the full transaction amount? TabaPay’s Partial Authorization Service provides an alternative to declining a transaction when the card’s available balance is not sufficient to approve a transaction in full. Participating issuers return a response with an approval for a portion of the original amount requested, enabling the remainder of the transaction amount to be paid by other means using split-tender functionality. You can increase sales and decrease declines by enabling customers to use all available prepaid or debit card funds, supplementing with an alternate payment method for a seamless purchase experience, ensuring satisfaction even with an uncertain remaining balance. | Highly Recommended | Yes | Yes |
| 3D Secure | Three-Domain Secure or 3DS is a messaging protocol merchants use to authenticate their customers’ card information when processing card-not-present (CNP) e-commerce, or mobile purchases, and payments. By enhancing authentication, 3DS helps prevent fraud and provides an additional layer of security for CNP credit card and debit card transactions.This service is provided by all four major card networks. | Highly Recommended | Yes | - |
| Account Name Inquiry | To help address growth in account takeover fraud and authorized push payment scams, market demand, and increasing concern from governments and regulators, card networks have introduced Account Name Inquiry (ANI) functionality. It enables an account cardholder’s name to be checked against the name held by their Issuing bank. | Highly Recommended | Yes | - |
| Address Verification | Address Verification Service (AVS) is a fraud prevention mechanism that reduces fraud and chargebacks. The service verifies if the card issuer recognizes the address provided by a cardholder. The results of the verification will help you determine whether to accept or decline a particular transaction or take further action. AVS is effective to both reduce fraud and reduce chargebacks. | Highly Recommended | Yes | Yes |
| CVV2 Verification | CVV Verification is a tool that helps verify if the cardholder has possession of the physical card. While it is not effective against lost or stolen card fraud, it is an additional check beneficial in e-Commerce channels since the Card security code is only printed on a physical card and is not available anywhere else. | Highly Recommended | Yes | - |
| Apple Pay and Google Pay Tokens | Up to the client | - | - | - |
| TabaPay Account Updater | TabaPay Account Updater (TAU) is a service that enables TabaPay clients who store cards on file with TabaPay to get them updated with the card networks to ensure they reflect the information available at the card issuer. This in turn addresses our client's need to run recurring payments and MIT on the cards on file without requiring their customer's to update them when the payment credential at the issuer has been updated. TAU significantly reduces customer friction, and meets the need to collect an updated card expiry date or payment credential since TabaPay automatically updates cards you store on file with us. | Highly Recommended at the Client level | - | - |
| TabaPay Tokens | TabaPay stores and manages payment cards and bank accounts securely for you. We call this TabaPay Tokens (aka TabaPay Vault). This capability allows you to be an efficient fintech while letting us manage the burden of PCI-DSS compliance for you. TabaPay takes on the complexities of storing these payment instruments safely and securely, while you to focus on your core value proposition! For every payment card or bank account, TabaPay validates the incoming payment instrument and stores them as an Account ID. This Account ID is what is provided back to you, so you do not have to manage the 16-digit payment card number or bank account. You will be able to utilize the Account ID within our Unified API (Create Transaction API) to Push and Pull. | Highly Recommended at the Client level | - | - |
Implementation Checklist
This checklist serves as a guideline for TabaPay clients interested in implementing this feature and includes, but not limited to, the following:
- Feature enablement of your use case.
- Sandbox integration
- Production integration
How the Create Transaction API Works for Account Funding
1. Prerequisites
Before connecting to then endpoint, ensure your IP is whitelisted as mentioned in step 4 of Integrating with TabaPay.
For this pull transaction, you will populate information differently for a card or bank payment within the Source Account object.
To enhance security, you can use TabaPay Tokens to generate unique IDs for card or bank details. Learn how Card Query APIs can use AVS to provide insights into how fraud controls influence transaction outcomes.
All requests should be in a compressed format.
Query Card
Query card may happen before the Create Transactionrequest.
- Query Card: TabaPay Client performs Query Card and checks for:
2. Create Transaction
Use the Create Transaction with type:pull. Depending on the payment features included, your API request body (parameters) will look different. Refer to the examples below in Recipes.
Refer to the following features with correlating indicators:
- Partial Auth: Authorize partial payment acceptance with
pullOptions.partial:true - 3DS: Follow the 3DS guide to set up the 3DS workflow.
- TabaPay Token: Include the Account ID, or Source Account ID you created with Create Transaction.
- Set Partial Authorization Flag: Set the partial field in pullOptions to true to indicate that partial authorization is requested.
- Handle Create Transaction Response: If the Create Transaction API response includes the partialAmount field, it indicates that the transaction was partially authorized.
- Transaction Submission: TabaPay sends the transaction request to the card network (for e.g with the Partial Authorization indicator enabled)
- Card Network Processing: The card network verifies the transaction and forwards it to the card issuer.
- Issuer Evaluation: The issuer reviews the transaction and approves the available balance on the card. If the available balance is less than the purchase amount, the issuer returns an authorization response to the card network. This response includes a unique code and the approved partial amount.
- Network Communication: The card network notifies TabaPay of the partial approval amount.
- TabaPay Client Notification: TabaPay informs the client of the authorization response.
- Customer Communication: The TabaPay client identifies the partialAmount field in the response, calculates the difference between the approved partial amount and the total transaction amount, and communicates this information to the cardholder.
- Cardholder Options: The cardholder has three options:
- Provide an Additional Payment Method: Use split-tender functionality to cover the remaining balance.
- Cancel the Transaction: Opt not to proceed with the purchase.
- Accept the Partial Purchase: Agree to load only $75 into their app account.
Note: This process aims to ensure a smooth and satisfactory experience for the customer. If the customer decides not to complete the sale, the TabaPay client should initiate an authorization reversal for the partial amount.
Recipes
Updated about 16 hours ago