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 (Yape): see the Transfer In overview for how each one is tokenized.

In Peru the response lists the Yape entry, which operates with payment flows. Choose the flow that matches the channel where the payer is:

`flowType`	Channel	How it works	Extra field in the token
`DEEPLINK`	Mobile	The payer is redirected straight to the Yape app, installed on their phone, to approve the payment.	—
`PUSH`	Web / Desktop	The payer enters their mobile number at your checkout and Yape sends a push notification to their app, where they approve the purchase from Approve purchases ("Aprobar compras").	`phoneNumber` required.

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

{ "processors": [ { "name": "Yape Processor", "currency": "PEN", "supportedFlows": [ { "type": "DEEPLINK", "name": "Deeplink", "description": "Mobile: redirección directa a la app de Yape" }, { "type": "PUSH", "name": "Push", "description": "Web / Desktop: notificación push al número Yape del pagador" } ] } ] }

Request

Responses