Khipu via dLocal

Accept Khipu payments with dLocal as the payment service provider (PSP).

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. Required fields must be present for the payment to succeed. Payrails sends Optional fields to the PSP when you include them.

Field	Status	Description
`amount.currency`	Required	Must be `CLP`. Payrails rejects other currencies.
`meta.customer.country`	Required	The customer’s country object. Payrails sends `CL` to dLocal for every Khipu payment, whatever `country.code` you send.
`meta.customer.name`	Required	Sent to dLocal as the payer name, together with `meta.customer.lastName`.
`meta.customer.email`	Required	Sent to dLocal as the payer email.
`meta.customer.identityCardNumber`	Optional	The customer’s RUT. Sent to dLocal as the payer document.
`meta.customer.lastName`	Optional	Added to the payer name.
`meta.customer.phone`	Optional	Sent to dLocal as the payer phone number.
`meta.order.billingAddress`	Optional	Sent to dLocal as the payer address. `meta.order.deliveryAddress` takes priority when both are present.
`meta.order.description`	Optional	Sent to dLocal as the payment description.
`meta.clientContext.ipAddress`	Optional	Sent to dLocal as the payer IP address.

Authorize a Khipu payment

Call authorize a payment with khipu as the paymentMethodCode. The response includes the redirect to the Khipu payment page. CLP has no minor unit, so send whole amounts.

Authorize request

{
  "amount": {
    "value": "15000",
    "currency": "CLP"
  },
  "paymentComposition": [
    {
      "integrationType": "api",
      "paymentMethodCode": "khipu",
      "amount": {
        "value": "15000",
        "currency": "CLP"
      }
    }
  ],
  "meta": {
    "customer": {
      "name": "Javiera",
      "lastName": "Soto",
      "email": "javiera.soto@example.com",
      "identityCardNumber": "123456785",
      "country": {
        "code": "CL"
      }
    }
  },
  "returnInfo": {
    "success": "https://example.com/success",
    "error": "https://example.com/error"
  }
}

After the customer confirms the transfer, they return to your 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.
Each Khipu payment is a new customer-initiated payment.

Getting Started

Payment Orchestration

Token Vault

Analytics & Reporting

Fraud Management

Chargebacks

Monitoring

Resources

Use Cases

Supported workflows

Before you begin

Request fields for dLocal

Authorize a Khipu payment

How dLocal handles Khipu

​Supported workflows

​Before you begin

​Request fields for dLocal

​Authorize a Khipu payment

​How dLocal handles Khipu

Supported workflows

Before you begin

Request fields for dLocal

Authorize a Khipu payment

How dLocal handles Khipu