How a Khipu payment works
Khipu is a redirect payment method:- The customer selects Khipu at checkout.
- Payrails returns a redirect URL from dLocal, and the customer goes to the Khipu payment page.
- The customer selects their bank, signs in, and confirms the transfer.
- The customer returns to your
returnInfoURL. - Payrails receives the final result from dLocal and updates the payment.
Supported currencies and countries
Khipu supports CLP (Chilean peso) as its only presentment currency.Supported workflows
Before you begin
Complete these steps before you send your first Khipu payment through dLocal:- Set up a dLocal integration in your workspace. Follow the dLocal integration setup guide if you don’t have one yet.
- Ask dLocal to enable Khipu on your dLocal account.
- In the Payrails Portal, go to Settings → Integrations, open your dLocal integration, select Khipu under Payment methods, and save.
- Add Khipu as a payment option in your workflow.
Request fields for dLocal
Send these fields in the authorize request, in addition to the standard authorize fields. Payrails checks Required fields and returns an error when one is missing. Fields required by the PSP pass the Payrails checks but the PSP can decline the payment without them.Authorize a Khipu payment
Call authorize a payment withkhipu as the paymentMethodCode. The response includes the redirect to the Khipu payment page. CLP has no minor unit, so send whole amounts.
Authorize request
success or error URL. Confirm the result through webhook notifications or the execution status before you fulfill the order.
How dLocal handles Khipu
- dLocal returns a redirect URL to the Khipu payment page. The payment stays pending until the customer confirms the transfer, and Payrails completes it from the dLocal notification.
- Cancel a Khipu payment only while it’s still pending, before the customer confirms the transfer. After that, refund the payment instead.
- Saving the instrument and merchant-initiated transactions (MIT) aren’t available.