Skip to content

Suggested
Dashboard
Sandbox Production

Payments / RailsOrigins and destinations

Origins and destinations

Reference for the payment-node entity, the rails available per country, and the valid origin and destination combinations per payment type.

Every payment defines its flow of funds through origins (where the money comes from) and destinations (where the money goes). Each entry is a payment-node: a type plus a sub-object that carries the configuration for that rail.

Only one node sub-object should be present per payment-node, matching the selected type.

Core fields

Section titled “Core fields”
FieldDescription
typeDefines the rail. Drives which sub-object is required.
currencyISO currency code. See Currencies.
amountPer-node amount. Required only when splitting funds across multiple nodes.
amountOutNet amount after fees. Read-only — returned by the platform.
nameDisplay name for the node — typically the provider or bank name. Defaults to conomy_hq.
settlementExpected settlement window for this rail.
feeFee applied to this node. Read-only — calculated and returned by the platform.
identityIdentity linked to the node — typically the account owner or the payer.
metadataDisplay metadata: image, description, and category for the node.
{node}Rail-specific data. The key matches the type in lowercase (e.g. "type": "PIX" → "pix": {...}).

Available rails

Section titled “Available rails”

Internal

TypeDescriptionDirection
ACCOUNTInternal account node—
BANK_ACCOUNTExternal bank accountPay-out

Argentina

TypeDescriptionDirection
CVUVirtual account identifierPay-in / Pay-out
PCTInteroperable QR transferPay-in

Brazil

TypeDescriptionDirection
PIXInstant payment railPay-in / Pay-out

Chile

TypeDescriptionDirection
ETPAYOpen banking redirectPay-in
FINTOCOpen banking widgetPay-in
WEBPAYCard and bank gatewayPay-in

Colombia

TypeDescriptionDirection
BANCOLOMBIADirect bank buttonPay-in
BREBBank payout railPay-out
DAVIPLATAMobile walletPay-in / Pay-out
DAVIVIENDADirect bank buttonPay-in
NEQUIMobile walletPay-in / Pay-out
PSEOnline bank transfer gatewayPay-in
WOMPIHosted checkout gatewayPay-in

Mexico

TypeDescriptionDirection
SPEICLABE bank transferPay-in / Pay-out

Peru

TypeDescriptionDirection
LIGOQR-based instant paymentPay-in
SIPInteroperable payment systemPay-in

USA

TypeDescriptionDirection
ACHBank transferPay-in / Pay-out
FEDNOWInstant bank transferPay-in / Pay-out
RTPReal-time paymentsPay-in
WIREWire transferPay-out

Venezuela

TypeDescriptionDirection
PAGO_MOVILMobile interbank paymentPay-in

Europe & UK

TypeDescriptionDirection
SEPAIBAN bank transferPay-out
FPEFaster PaymentsPay-out

International

TypeDescriptionDirection
SWIFTInternational wirePay-out
CRYPTOWallet transferPay-in / Pay-out

Valid combinations per payment type

Section titled “Valid combinations per payment type”
Payment typeValid originsValid destinations
TOPUP_ACCOUNTAny pay-in railACCOUNT
WITHDRAWAL_ACCOUNTACCOUNTAny pay-out rail
PURCHASEAny pay-in railACCOUNT
REMITTANCEACCOUNT or any pay-in railAny pay-out rail
P2PACCOUNTACCOUNT
COLLECTACCOUNTACCOUNT

Rules

Section titled “Rules”
  • If a payment has a single origin and a single destination, amount per node is optional — it defaults from the selected root amount mode (purchaseAmount or totalAmount).
  • If a payment has multiple origins or destinations, every node must carry an amount and the sums must equal the selected root amount mode.
  • Only the sub-object matching type is allowed on a node. Send "type": "PIX" together with "pix": {...} and nothing else.