Kushki's Online Payments API covers the full payment lifecycle for Chile 🇨🇱: collect money from your customers via card, bank transfer, or cash; disburse funds to third parties; manage recurring subscriptions; create hosted payment pages; and access transaction records for reconciliation and reporting.
Supported currency#
| Currency | Code | Notes |
|---|
| Chilean Peso | CLP | Integer amounts only — no decimal places |
The Chilean Peso has no decimal places. Always send amounts as whole numbers (e.g., 10000, not 10000.50). Decimal values will result in a 400 Bad Request.
Document types#
| Value | Description |
|---|
RUT | Rol Único Tributario 🇨🇱 |
CE | Cédula de Extranjería 🇨🇱 |
PAS | Pasaporte 🇨🇱 |
Collect payments (Pay-in)#
Card
Accept credit and debit card payments — single charges, Cuotas Comercio, Cuotas Emisor, pre-authorization flows, 3DS, network tokens, and zero-amount card verification.
Card Async
Collect card payments asynchronously — tokenize the card, initialize the charge, and receive the final result via webhook once processing completes.
One-Click & Scheduled Payments
Save a card once and charge it on demand or on a recurring schedule — without asking the customer for card details again.
Transfer In
Accept bank transfer payments — redirect the customer to their bank's portal and receive a confirmation once the transfer completes.
Cash In
Accept cash payments at physical collection points — Kushki generates a PIN that the customer presents to pay.
Disburse funds (Pay-out)#
Transfer Out
Send funds directly to a recipient's bank account — disbursements, supplier payments, and payouts via bank transfer.
Async recurring charges#
Async Card Recurring Charges
Run scheduled recurring charges against saved async card subscriptions — token creation, subscription init, pre-authorization, and capture flows.
Smartlinks V2
Create hosted payment pages and share a URL with your customers — no frontend integration required. Supports card, transfer, and subscriptions.
Payment Button
Embed a Kushki-hosted checkout button directly into your website or e-commerce platform.
Merchant management#
Payment Credentials
Create, rotate, activate, and delete API key pairs for your merchant account programmatically.
Reporting & reconciliation#
Analytics
Query your full transaction history — paginated, with flexible filters for date, payment method, status, and type. Use v2 for the most complete dataset.
Settlement
Retrieve settlement records by date range or ticket number — including transaction amounts, Kushki fees, and the net amount paid to the merchant.
Chargebacks
Search and export chargeback records — filter by status, date, and type. Export asynchronously via webhook notification.
Subscription Transactions
Query the transaction history for a specific subscription — all charges, statuses, and amounts in one place.
Status & monitoring#
Service Status
Check the operational status of Kushki's payment gateway and core platform services in real time.
Common request pattern#
Most pay-in operations follow a token → charge flow: sensitive data is tokenized on your backend first, then the token is used to submit the charge. Your server never needs to store raw card or bank account data.1. POST /card/v1/tokens → one-time token
2. POST /card/v1/charges → charge using the token
Authentication#
All endpoints use your merchant keys in the request headers. Use Private Key for all server-to-server calls; never expose it in frontend code.Some operations (e.g., BIN lookups initiated from the browser) accept the Public Key:
Using the API#
https://api.kushkipagos.com/
When a card requires OTP validation in the sandbox environment, use 555 for CLP transactions.
Got a suggestion on this documentation? Contact us.
