For the complete documentation index, see llms.txt
For the complete documentation index, see llms.txt
tw
Help center
Integrating Tabapay for Instant Debit Card Funding on Unit Deposit Accounts
# Tabapay Integration for Instant Debit Card Funding on Unit
## Introduction
Tabapay allows your end customers to instantly fund their Unit deposit accounts using an external debit card, significantly reducing the time-to-first-use compared to traditional ACH processes. It connects across all major debit card networks to maximize efficiency and cost-effectiveness.
## Customer Experience
1. After issuance of a Unit debit card to your end customer, prompt them to fund their account using an external debit card.
2. Customers enter the funding amount and their external debit card details similar to an ecommerce checkout.
3. Upon successful transaction, funds are pushed immediately to the activated Unit debit card, reflected instantly in the deposit account.
4. Customers may be prompted to authenticate via 3D Secure (e.g., SMS one-time passcode) depending on their card issuer. Authentication is completed within your UI.
## Implementation Details
### Partner Agreements
You will contract directly with Tabapay, becoming a Merchant. The onboarding includes:
- Mutual Non-Disclosure Agreement (NDA)
- Merchant Application for purchase and disbursement services
- Merchant Agreement with pricing terms
### Compliance
Your bank partner must provide an Agency Letter to Tabapay to authorize participation. Unit supports facilitating this.
### Technical Integration
#### User Interface
- Tabapay provides a fully customizable, PCI-compliant widget to securely collect external debit card details.
- Postal code may be required for Address Verification Service (AVS).
- Support 3D Secure authentication through Cardinal Commerce SDK, available for iOS and Android, to handle issuer-specific verification like one-time passcodes.
#### Enable Card-to-Card Payments via API
Use the Unit PATCH API endpoint to enable card-to-card payments by submitting Tabapay client ID and token under 'cards-write' scope.
- Endpoint: `PATCH https://api.s.api.unit.sh/cards/{cardId}/enableCardToCardPayment`
- Required attributes: `clientId`, `token`, optional `idempotencyKey`
Example cURL:
```bash
curl --request PATCH 'https://api.s.unit.sh/cards/21/enableCardToCardPayment' \
--header 'Content-Type: application/vnd.api+json' \
--header 'Authorization: Bearer $UnitToken' \
--data-raw '{
"data": {
"type": "tabapay",
"attributes": {
"clientId": "$TabapayClientId",
"token": "$TabapayToken"
}
}
}'
```
#### Important
Whitelist VGS's IP addresses for sandbox and production environments.
### Testing and Certification
Testing individual components in sandbox is important but cannot fully replicate live environment flows such as push to card and account funding. Full end-to-end testing must be performed in the live environment before launching broadly to customers.
## Dashboard
- All card transactions via Tabapay appear as CardTransaction records on your deposit accounts.
- Merchant details will reflect those specified in your funding and disbursement requests to Tabapay.
- Transactions appear in your Unit Dashboard for monitoring.
## Additional Resources
- Tabapay website: https://tabapay.com/
- 3D Secure overview: https://developers.tabapay.com/docs/overview-of-3ds
- Cardinal Commerce iOS SDK docs
- Cardinal Commerce Android SDK docs
- VGS IP whitelisting docs: https://www.verygoodsecurity.com/docs/faq#ip-addresses-to-whitelist
This integration optimizes customer onboarding and deposit funding speed by leveraging instant debit card transfers via Tabapay.
