Zynk
Getting StartedProduct GuidesAPI ReferenceFAQ'sRecipes
Getting StartedProduct GuidesAPI ReferenceFAQ'sRecipes
  1. Accounts & Wallets
  • Transformer - Cross Border Transfer
    • Overview
    • Customers & Identity
      • Entities/Customers
      • About KYC/KYB
      • RFI Scenarios for Customers
      • Identity Rejection Reasons
    • Accounts & Wallets
      • External Accounts(To be deprecated soon)
      • Fetch Requirements for External Accounts V2
      • External Accounts V2
      • Funding Accounts
      • About Plaid Integration
    • Transfers
      • Counterparty Risk details
      • Addition transfer requirements
      • Transfer in Action
      • Limits and Minimums
      • Fee details
    • Miscellaneous
      • Bank Codes
      • Supported chains and currencies
      • Partner payments signature generation
      • Reserves requirements
      • Partner Payments
      • Status updates - Webhooks
  • Transporter - Automated Liquidity Manager
    • Overview
    • Visibility Protocol
    • Instant liquidity process - How it works
    • Status updates - Webhooks
  • Teleport - Pay-In Accounts
    • Overview
    • About Teleport routes
  • Warp - Pay-Outs
    • Overview
  • Continuum - Wallet Infrastructure
    • Overview
    • Authentication
    • Continuum APIs
    • Transactions on Continuum
    • Details on generating signatures
Getting StartedProduct GuidesAPI ReferenceFAQ'sRecipes
Getting StartedProduct GuidesAPI ReferenceFAQ'sRecipes
  1. Accounts & Wallets

External Accounts

To be deprecated soon
For pay-in flows where customers want to give Fiat and receive crypto, partners should add both source bank account and crypto wallet of customer as accounts separately.
For payout flows where customers want to give crypto and receive FIAT, partners should add both receiving bank account and source crypto wallet as accounts separately.
For FIAT to FIAT flows partners should add both source bank account and receiving bank account separately.
The payload for Add Accounts API differs for each FIAT jurisdiction. The details are static and can be used to generate payload for Add accounts API when adding a FIAT account.
Some payloads require a bank code. Please find the list of different bank codes here.
BRL(Brazil FIAT)
AED
MXN (Mexico)
ARS (Argentina)
PHP (Phillipines)
IDR (Indonesia)
USD
EUR
INR
{
  "jurisdictionID": "jurisdiction_...",
  "account": 
    {
       "documentType": "CNPJ", //CPF or CNPJ
       "documentNumber": "1234567890123", //numeric string between 11-14 digits
       "pixKeyType": "EMAIL", //CPF, EMAIL, or PHONE
       "pixKey": "miracarslan95558981199@gmail.com", //between 8 and 50 characters
       "beneficiaryType": "individual", //individual or business
       "payerName": "Mirac Arslan"
    }
}
Note:
Whitelisting for payouts in AED jurisdiction:
For Payout flows we have an additional whitelisting requirement, where partners need to provide us with following:
Partners to provide customerId and customerName which partners store in their system for each entity
Partners should also provide a whitelisting API which when called with the customerId given above should return the source wallet of the customers.
This is a mandatory requirement and cannot be skipped to remain compliant with AED jurisdiction government regulations
Whitelisting for payouts in AED jurisdiction:
In AED jursidiction customers should only make FIAT depoist from accounts they add as part of Add Accounts API call. This is an important requirement for us to ensure we comply with local regulations. Any money, that is transferred to the destination bank account from a different bank account, gets returned in 24 hrs to the source account and Zynk won't be able to process the transaction for the same.
Modified at 2025-11-14 15:00:27
Previous
Identity Rejection Reasons
Next
Fetch Requirements for External Accounts V2
Built with