Request a Transfer In token

A Transfer In token will allow you to start a Transfer In transaction.

Token expiration
Tokens will expire in 30 minutes and can be used only for a single transaction (even if the transaction was wrong). You will need to request a new token when it expires.

🚧 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.

🇵🇪 Peru — Yape flows (DEEPLINK / PUSH)

To pay through Yape, send the optional processor object copying the values returned by Get Transfer In configuration (GET /transfer/v1/config): "processor": { "name": "Yape Processor", "flowType": "DEEPLINK" | "PUSH" }. Pick the flow for the payer's channel — DEEPLINK for mobile, PUSH for web or desktop. When you send processor, only amount and currency remain required; the PUSH flow additionally requires phoneNumber (the payer's Yape number). Yape operates only in PEN.

The traditional integration is unchanged: a token without processor behaves exactly as before.

Direct API integrations only: request the token from your backend. Kajita and Kushki.js do not support the processor object yet.

curl --location 'https://api-uat.kushkipagos.com/transfer/v1/tokens' \ --header 'Public-Merchant-Id;' \ --header 'Content-Type: application/json' \ --data-raw '{ "amount": { "subtotalIva": 100000, "subtotalIva0": 0, "iva": 10000, "extraTaxes": { "tasaAeroportuaria": 0, "agenciaDeViaje": 0, "iac": 0 } }, "callbackUrl": "https://kushki.com", "userType": "1", "documentType": "DNI", "documentNumber": "12345678", "paymentDescription": "Description of the payment.", "email": "user@example.com", "currency": "PEN" }'

Token expiration#

Request

Responses

Token expiration