Get Transfer In configuration

🚧 Early Release — Beta

This product is in early access. Parameters, response structures and behaviors may change without prior notice. Do not use this version in production without first coordinating with the Kushki integrations team.

Returns the Transfer In processors enabled for your merchant and, when applicable, the payment flows each one supports.

Use it before tokenizing

Call this endpoint before requesting a token to know which processors are available and how to build the token for each one:

An entry without supportedFlows is a traditional processor: request the token without the processor object, exactly as today.

An entry with supportedFlows operates with payment flows: request the token with processor: { name, flowType }, copying name from processors[].name and flowType from one of processors[].supportedFlows[].type.

If your merchant has several processors, use the supportedFlows of each entry to decide how to build each token. Entries with supportedFlows operate through payment flows (Bre-B): see the Transfer In overview for how each one is tokenized.

In Colombia the response can list two kinds of entry:

Entry	`supportedFlows`	How to tokenize
PSE	Absent	Traditional flow: request the token without the `processor` object and send the fields PSE requires (`bankId`, `callbackUrl`, `userType`, `documentType`, `documentNumber`).
Bre-B	`QR`	Request the token with `processor: { name, flowType }` and `flowType: "QR"`. `bankId` does not apply.

If the merchant has no Transfer In processors configured, the response is 200 with an empty processors array.

{ "processors": [ { "name": "Pse Processor", "currency": "COP" }, { "name": "Bre-B Credibanco Processor", "currency": "COP", "supportedFlows": [ { "type": "QR", "name": "QR Code", "description": "QR code payment" } ] } ] }

Request

Responses