Skip to main content
WebPay is the online payment page of Transbank in Chile. Customers pay with a Chilean debit or credit card on the WebPay page, so card details never pass through your checkout. Payrails processes WebPay through two payment service providers (PSPs): dLocal, and Transbank directly. The flow is the same with each one, but the required request fields and the supported workflows differ. Pick a PSP below for its setup steps and request examples.

​
How a WebPay payment works

WebPay is a hosted payment page:
  1. The customer selects WebPay at checkout.
  2. Payrails returns a redirect from the PSP, and the customer goes to the WebPay page.
  3. The customer enters their card details and confirms the payment.
  4. The customer returns to your returnInfo URL.
  5. Payrails receives the final result from the PSP and updates the payment.
Each payment is single-use: the customer confirms every payment on its own. To return funds, refund the payment. Refunds work with both PSPs.

​
Supported currencies and countries

WebPay supports CLP (Chilean peso) as its only presentment currency. Payrails rejects WebPay payments in any other currency.

​
Integrate WebPay

Choose the PSP that processes WebPay for you. Each guide covers the PSP-side setup, the Payrails configuration and the request fields that PSP requires.

dLocal

WebPay via dLocal

Transbank

WebPay via Transbank

​
Compare PSPs

Delayed capture works only with Transbank, on a Transbank account set up for deferred capture. Save Instruments and merchant-initiated transactions (MIT) aren’t available for WebPay with either PSP.

​
Ways to integrate WebPay

  • Payrails SDK: the Web SDK shows WebPay when your workflow returns it as a payment option, and redirects the customer to the WebPay page. To control how the redirect opens, listen for the actionRequired event.
  • Payrails API: call lookup payment options, then authorize with webPay as the paymentMethodCode. Each PSP guide lists the meta fields that PSP requires.
In both cases, confirm the final result through webhook notifications or the execution status. Don’t treat the customer’s return to your success URL as proof of payment.
Last modified on October 2, 2026