Skip to main content
Payouts support fund transfer networks, allowing visibility into—and where supported, selection of—the actual network used to deliver funds. Local payouts expose multiple networks per corridor (e.g., IMPS and NEFT for India). Certain SWIFT corridors routed via a correspondent bank (CRB) also carry a fund transfer network (cross_border_wire).

​
Payout Object

​
New Fields

A new optional local object is added to the payout object. Notes
  • Represents the actual network used to deliver funds
  • Certain corridors allow Tazapay users to specify the network; for others it is auto-populated
  • Returned in all payout API responses and payout webhooks

​
Payout Bank Metadata API

​
New Fields

The payout bank metadata response includes fund_transfer_networks.

​
fund_transfer_networks (array)

Each object contains: Transfer Limit Rules
  • Limits may vary by network
  • Effective payout method limits are derived as:
    • Min limit: max of all network minimums
    • Max limit: min of all network maximums
Each network entry also carries capability fields — delivery_time, on_behalf_of_supported, supported_modes, restricted_purpose_codes and cutoff_schedule. See Using Payout Capability Fields.

​
Querying by fund transfer network

Pass fund_transfer_network as a query parameter to the Payout Bank Metadata API to retrieve only corridors for a specific network.

​
SWIFT Correspondent Bank (CRB) Routing

Certain SWIFT corridors are routed via a correspondent bank and carry the network identifier cross_border_wire. In the Tazapay dashboard and user-facing interfaces this network is displayed as Cross-border USD Wire (via Fedwire/SWIFT); cross_border_wire is the value used in all API requests and responses.

​
Payout Object

A new optional swift object is added to the payout object for SWIFT-type payouts. Notes
  • Pass cross_border_wire to explicitly route the payout via a correspondent bank
  • Returned in all payout API responses and payout webhooks when the payout is CRB-routed
  • Omit the swift object for standard SWIFT payouts — routing is handled automatically

​
Payout Bank Metadata API

The metadata response was updated to expose CRB corridors distinctly from standard SWIFT corridors, so integrations can:
  • Discover which corridors support CRB routing and what limits apply
  • Display the correct network name (Cross-border USD Wire (via Fedwire/SWIFT)) to end users
  • Quote accurate transfer limits for CRB-routed payouts, which may differ from the corridor-level limits
These corridors appear in the metadata response with:
  • payout_type: swift
  • fund_transfer_networks: [{ name: "cross_border_wire", transfer_limit: { ... } }]
Query the metadata API with fund_transfer_network=cross_border_wire to retrieve only CRB corridors:
  1. Create Payout
  2. Payout Bank Metadata API
  3. Using Payout Capability Fields