Webpay Plus Payments

Accept payments using Webpay Plus as an alternative for your customers and provide trust in the transaction

Web

Android

iOS

This functionality is available for the following models:

☐ Acquirer

☑ Aggregator

Kushki allows your business to offer payments through Transbank's Webpay Plus. Your customers will be able to shop using credit cards, RedCompra debit cards, prepaid cards, and through OnePay. It is the most common type of online transaction in Chile.

If you are interested in generating on-demand payments for debit, check our on-demand payment guide on Webpay Oneclick.

Unlike other forms of integration, in this one, the customer will be redirected to a Transbank payment portal and to their bank to complete the transaction.

To keep in mind

Due to our risk policies, the available payment methods and the integration type may vary once you complete the affiliation. We will tell you how to proceed if this process applies to your merchant.

How does it work?

A payment flow on Webpay usually consists of the following steps:

The user starts the payment process on your website or app.

The user is redirected to the Webpay portal to make the payment, where his/her card details should be entered.

Then, the user is taken to the credit card issuer's portal (a bank or other financial entity) where the customer's identity is authenticated using his/her credentials.

Once the authentication has been completed, the payment is authorized and the user is taken back to your website.

A message notifying the user of the success or failure of the operation will be displayed, depending on the result of the payment.

The flow that you will integrate is shown below:

1. Set up your Front-end

The front-end is responsible for collecting the user’s card details securely, generating a token for such information through Kushki’s servers, and sending that information to the back end to start the payment process.

You have two options to integrate: Kajita and Kushki.js.

Kajita

Kushki has payment forms ready to collect card information securely. You can use any of our versions:

Cajita: the first version of the predefined payment form. Not customizable.

Kajita: the second version. It allows you to customize your payment forms from your Administration Console and even have several versions of Kajita, for example, one for each payment method.

Create and customize your Kajita

With Kushki you can create your Kajitas from the Administration Console. Click here to learn how to do this.

Set up Kajita

Include the kushki-checkout.js script in your payment page by adding it to the <head> of your HTML file. Always load kushki-checkout directly from cdn.kushkipagos.com. Do not include the script in a bundle or package or host a copy of it.

Cajita needs a place to live on your page. Enter the following code in your website's <body>, where you want the payment form to be displayed.

Add Kajita to your Website

Kajita needs a space within your page. Enter the following code in your website's <body>, where you want the payment form to be displayed.

For Kajita (v.2):

For Cajita (v.1):

Remember to configure the action of the action form according to the corresponding endpoint in your back end.

Then, add the following script tag. Make sure that the form has been uploaded.

You must add the variable return_url, which is where the user will return after completing the payment process in the Webpay portal.

This will create a predesigned form on your website to accept payments.

You can use Cajita to offer not only card payments, but also in cash and wire-transfer.

Kushki.js

Use Kushki.js if you need more control over the "look & feel" or appearance of your payment form.

Set up Kushki.js

Option 1 - CDN

Use the following script tag at the end of the <body> of your payment page.

Option 2 - NPM

Install the package from npm.

Then import it into your code using the following code.

Set up `Kushki` object

Add the following code to your application

Collect User Information and Send it to your Back End

You may collect users' data as you prefer. For this case, we only need an e-mail address, so you can provide it directly if you already have this information, or include an email field for the user to enter their address.

Once you have the user's email address, add a Kushki token request to send it to your back end, as shown below:

Check the full reference on our Kushki.js reference

2. Set up your Back End

The back end is responsible for receiving the token obtained from your front end and starting the payment process with Kushki.

When the user submits the form, your front end sends a token to an endpoint that you specified previously. Using this token, you must make a call to our [Webpay Plus charge endpoint] (https://api-docs.kushkipagos.com/chile/online-payments/card-async/init) to start the charge and redirect the user.

JavaScript

Check our API Reference for more information.

As a response to the call, you will obtain the variable redirect_url that you must use to redirect the user to the Webpay payment portal to proceed to the payment.

For redirecting, try not to use containers such as Frame, Panel, or IFrame. Also, avoid using functions such as pop-up windows, as they can be blocked by the browser. Redirect the user within the same tab or window.

3. Capture the Response

Once the payment is complete, the customer will be taken back through a GET call to the return_url provided as a parameter in step 1. This call will be accompanied by a parameter called token placed in the path, which stands for the transaction's unique identifier.

For example, for return_url = "http://www.example.com/return the customer will be taken back to:

GET http://www.example.com/return?token=020199203102301203

where token is equal to 020199203102301203

According to the response you receive, it shows the user a success or failure page to inform the customer if the subscription was created correctly, or if an error occurred.

4. Test your Integration

You can use some test cards in test mode to ensure that your integration is ready.

Approved transaction

Card number: 4051885600446623

CVV: 123

Expiration date: Any date in the future

RUT: 11.111.111-1

Password: 123

Transaction declined

Card number:`5186059559590568

CVV: 123

Expiration date: Any date in the future

5. Prepare your Certification

Read the following guidelines for technical certification approval (required to obtain productive account credentials):

Tax calculations must be correct.

Messages displayed on the screen should be aligned with Kushki's responses.

All Kushki responses must be saved and recorded (required in case you need support).

Kushki's logo must be visible for the customer. You can find our logo in several formats here.

If you are using Kushki.js, also check the following:

The payment button must be disabled after the first click.

Kushki's logo must be visible for the customer. You can find our logo in several formats here.

Accept payments with OTP

Only Web. OTP (One Time Password) is an extra layer of protection against online fraud.

Accept Webhooks

Manage correctly post-payment events.

Explore this section

Reserve funds with Webpay PlusReserve funds and capture them laterRead article →

How does it work?#

1. Set up your Front-end#

Kajita#

Create and customize your Kajita#

Set up Kajita#

Add Kajita to your Website#

Kushki.js#

Set up Kushki.js#

Option 1 - CDN#

Option 2 - NPM#

Set up Kushki object#

Collect User Information and Send it to your Back End#

2. Set up your Back End#

3. Capture the Response#

4. Test your Integration#

Approved transaction#

Transaction declined#

5. Prepare your Certification#

Explore this section#

How does it work?

1. Set up your Front-end

Kajita

Create and customize your Kajita

Set up Kajita

Add Kajita to your Website

Kushki.js

Set up Kushki.js

Option 1 - CDN

Option 2 - NPM

Set up `Kushki` object

Collect User Information and Send it to your Back End

2. Set up your Back End

3. Capture the Response

4. Test your Integration

Approved transaction

Transaction declined

5. Prepare your Certification

Explore this section