Zynk
Getting StartedProduct GuidesAPI ReferenceFAQ'sRecipes
Getting StartedProduct GuidesAPI ReferenceFAQ'sRecipes
  1. Transporter - Automated Liquidity Manager
  • 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. Transporter - Automated Liquidity Manager

Visibility Protocol

Zynk's Transporter Protocol requires visibility into the source of transactions for which liquidity is being requested. It serves as an audit for transaction, only for those transactions that are actively in-transit on the Partner’s platform.
Typical Fund Flow:
A. The end user (KYC-verified) initiates a fiat/stablecoin transfer/purchase/conversion
B. The fiat deposit is initiated and en route to the Partner’s custody (may involve banking rail delays)
C. The Partner requests liquidity from Zynk to bridge the delay
D. Zynk provides liquidity for that specific transaction
E. The fiat settles into the Partner’s custody and is then settled into the destination
F. The Partner replenishes Zynk for the liquidity provided

Zynk’s Requirement for Visibility#

Zynk requires direct visibility into steps A, B, and E. While steps C, D, and F are already managed through Zynk’s APIs described above, visibility into the source-level events of steps A, B, and E is crucial.
Zynk requests that Partners share the same mechanism they use internally to track these events — such as webhooks received from systems banking systems.
Zynk must receive original source data, not intermediary or wrapper data that has been modified or abstracted by the Partner’s internal systems.
Zynk will provide a url( {{baseURL}}/api/v1/webhook/ops/alm ) to partners to submit event data for visibility steps. Please use x-api-token in headers as authentication for the url provided.

Required events#

We request our partners to send the below events as part of the visibility protocol.
FIAT to FIAT
Mandatory events:
E1
      {
"eventType": "transactionInitiation",
"txnId": "12dfgh56"
"paymentMode": "VISA"/"MASTERCARD"/"ACH" 
"senderDetails":
     {
      "accountNumber": "xxxx688",
      "accountName": "ABD",
               },
"txnAmount": 500,
"currency": "USD",
"timestamp": "2025-11-26T10:11:36.000Z"

}
E2
{
"eventType": "transactionSettlement",
"txnId": "12dfgh56"
"paymentMode": "UPI" "NEFT" etc
"receiverDetails":
     {
      "accountNumber": "xxxx688",
      "accountName": "ABD",
               },
"txnAmount": 50000,
"currency": "INR",
"timestamp": "2025-11-26T10:11:36.000Z"

}
      
      
Optional Events:
E3
{

"eventType: "fiatSettled",
"txnId: "12dfgh56",
"timestamp": "2025-11-26T10:11:36.000Z"

}
E4
Send this event if you want us to ignore the transaction when doing our internal reconciliation. This is for cases where a transaction that was initiated could not be settled at your end.
{
"eventType: "abandonTransaction"
"txnId: "12dfgh56"
"timestamp": "2025-11-26T10:11:36.000Z"

}
FIAT to STABLE
STABLE to FIAT
Modified at 2025-12-02 14:10:57
Previous
Overview
Next
Instant liquidity process - How it works
Built with