Khipu

Khipu enables payments through bank transfers directly from the payer’s account. The experience can be completed either within their bank’s platform or through the Khipu website, which provides a faster and seamless payment flow.

Payment Flow

Enter Email Address - The payer starts by entering their email address to receive the payment receipt and confirmation.
Select Bank or Account Type - The system displays a list of available banks. The payer selects whether the payment will be made from a personal or business account.
Log In to Bank - The payer is redirected to their bank’s login screen and enters their RUT and password. This step securely connects their online banking account through Khipu.
Choose the Account - Once logged in, the payer selects the specific bank account to be used for the transfer.
Authorize the Payment - The payment details (amount and merchant) are shown for review. The payer authorizes the transaction by entering their security code or token.
Confirmation - After authorization, a confirmation screen appears showing the payment amount, merchant, and reference code. A digital receipt is sent to the payer’s email, and they’re redirected back to the merchant’s site automatically.

↪️
Redirect Flow for Khipu
This payment method uses a Redirect flow. The API response includes an Action and the purchase remains in Pending status until the customer completes the payment in the Internet Banking.

Request parameters

The following parameters are required specifically for this payment method.
Refer to the Purchase operation guide for standard fields and authentication requirements.

Property	Type	Mandatory?	Description
`PaymentMethod`	`string`	Yes	`KHI` – Find the value in the table Payment Method.
`TargetCountryISO`	`string`	Yes	Must be `CL`.
`Customer` → `Email`	`string`	Yes	Customer’s email.
`Customer` → `FirstName`	`string`	Yes	Customer’s first name.
`Customer` → `LastName`	`string`	Yes	Customer’s last name.
`Customer` → `DocumentType`	`string`	No	Customer’s document type. Use `RUT.CL`.
`Customer` → `DocumentNumber`	`string`	No	RUT without dots or hyphen. Example: `111111111`.
`Customer` → `PhoneNumber`	`string`	No	Customer’s phone number.
`Customer` → `Address` → `Country`	`string`	No	Customer’s country.
`Customer` → `Address` → `State`	`string`	No	Customer’s region.
`Customer` → `Address` → `City`	`string`	No	Customer’s city.
`Customer` → `Address` → `AddressDetail`	`string`	No	Customer’s address line.
`Customer` → `Address` → `PostalCode`	`string`	No	Customer’s postal code.
`Redirection` → `Url_Approved`	`string`	No	Callback URL when the purchase status is Approved.
`Redirection` → `Url_Rejected`	`string`	No	Callback URL when the purchase status is Rejected.
`Redirection` → `Url_Canceled`	`string`	No	Callback URL when the purchase status is Canceled.
`Redirection` → `Url_Pending`	`string`	No	Callback URL when the purchase status is Pending.
`Redirection` → `Url_Notify`	`string`	No	Webhook notification URL. The purchase status is notified to this URL once the payment processor confirms the status.
`MetaDataIn` → `PaymentExpirationInMinutes`	`numeric`	No	Defines the expiration time for the payment in minutes. The API applies a default value if omitted.

Request example

To test this endpoint, use the API Reference or the Postman Collection

{
  "PaymentMethod": "KHI",
  "Order": "CL-KHIPU-0001",
  "Amount": 25000,
  "Currency": "CLP",
  "Description": "Compra online - Khipu test",
  "TargetCountryISO": "CL",
  "Customer": {
    "FirstName": "Camila",
    "LastName": "Muñoz",
    "Email": "[email protected]",
    "DocumentType": "RUT.CL",
    "DocumentNumber": "111111111"
  },
  "MetaDataIn": {
    "PaymentExpirationInMinutes": 7200
  },
  "Redirection": {
    "Url_Approved": "https://mitienda.cl/checkout/aprobado",
    "Url_Rejected": "https://mitienda.cl/checkout/rechazado",
    "Url_Canceled": "https://mitienda.cl/checkout/cancelado",
    "Url_Pending": "https://mitienda.cl/checkout/pendiente",
    "Url_Notify": "https://webhook.site/9e2dff8b-cec6-4540-bd2d-feafce58a9ed"
  }
}

Response parameters

The API returns the purchase with Status PENDING and includes an Action object where:

Reason = REDIRECTION_NEEDED_EXTERNAL_SERVICE
URL = Link to redirect the payer to the Khipu page.

The merchant must redirect the payer to this URL so they can log in and complete the payment. For more information on the response parameters, please refer to the Response parameters section of the Purchase creation.

ℹ️
When testing, if RUT and password are requested, use: RUT: 11.111.111-1 Password: 123

Response example

{
  "TransactionId": "79632697147789184",
  "Result": "ACTION_REQUIRED",
  "Status": "PENDING",
  "ErrorCode": null,
  "ErrorDescription": null,
  "Created": "2024-08-07T17:51:54.620",
  "AuthorizationDate": null,
  "AuthorizationCode": null,
  "Amount": 25000,
  "Currency": "CLP",
  "Installments": 1,
  "Url": "https://api.stage.bamboopayment.com/Purchase/79632697147789184",
  "MetadataOut": null,
  "Action": {
    "SessionId": "CA_f1696826-3607-47ef-adba-94291876758b",
    "URL": "https://redirect.stage.bamboopayment.com/CA_f1696826-3607-47ef-adba-94291876758b",
    "Reason": "REDIRECTION_NEEDED_EXTERNAL_SERVICE"
  },
  "PaymentMethod": {
    "Brand": "Khipu",
    "Type": "BankTransfer"
  }
}

Discover the API

Once you’re familiar with how to create a purchase, you can test your integration using our API Reference

Country Requirements

Check what each country requires in terms of documents, bank formats, and supported currencies.

Create a Payment

Explore full request and response examples.

Error Codes

Understand possible error responses and how to resolve them.