Zynk
Getting StartedProduct GuidesAPI ReferenceFAQ'sRecipes
Getting StartedProduct GuidesAPI ReferenceFAQ'sRecipes
  1. Transfers
  • 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. Transfers

Addition transfer requirements

2FA for ACH PULL Transfer methods#

In certain Transfer scenarios where partners are utilising the ACH pull payment method for USD corridors, it is mandatory to implement a 2FA method.
Partners can implement the 2FA at their end or utilise the Zynk 2FA.
Please note Zynk will not enable production setup for ACH pull unless it can see proof of 2FA implemented in the production flow at partner's end.

Process of Zynk 2FA#

Zynk currenty supoprts only EMAIL-OTP based 2-factor authentication. The OTP will be sent to the registered users/entitites email id which is provided druring Create Entity
1
Get 2FA enabled after discussing with Zynklabs tech for your partner-Id
The process is currently manual
2
Entities receive OTP
When Simulate API is called, users will receive an OTP on their email
3
Submit OTP
Submit OTP using the optional field verificationCode in Transfer API
Modified at 2025-11-11 14:15:24
Previous
Counterparty Risk details
Next
Transfer in Action
Built with