Authorizes the separation of funds from a card, to capture them laterThis functionality is available for the following models:
☐ Acquirer
☑ AggregatorThe amount to be captured must be equal to or less than the authorized amount.
You can make multiple partial captures as long as their sum does not exceed the authorized amount.
How does it work?#
A Webpay payment flow generally consists of the following steps:1.
The user initiates the payment process on your site or app.
2.
The user is redirected to the Webpay portal to make the payment, where they enters their card data.
3.
Then, they go to the card issuer's portal (the bank or other financial institution) where they authenticate using their credentials.
4.
Once the authentication is completed, the payment is authorized and the user returns to your site.
5.
A success or failure message is displayed depending on the result of the payment.
2.
Initiate the authorization with Kushki.
3.
Kushki will try to perform the authorization with the card issuer.
4.
If the response is positive, the merchant will be able to capture an amount and charge the customer's card.
Kajita#
Kushki has payment forms ready to collect card information securely. You can use any of our versions:Cajita: the first version of the payment form. It is 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. Create and customize your Kajitas#
With Kushki you can create your Kajitas from the Administration Console. Click here to learn how to do it.Include the kushki-checkout.js script in your checkout 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.Add Kajita to your site#
Kajita needs a space within your page. Enter the following code in the <body> of your site where you want the payment form to be displayed.Remember to configure the action of the action form according to the corresponding endpoint in your back-end, to get the token.Then, add the script tag. Make sure the form has loaded.For Kajita (v.2) you will be able to get the script from your Admin Console as explained here.For v.1 (Cajita), add the following script. It is important that you add the variable return_url which is where the user will return once the payment process is completed in the Webpay portal.This will create a predefined form on your page to accept payments.Kushki.js#
Use Kushki.js if you need more control over the look & feel of your card form.Option 1 - CDN#
Use the following script tag at the end of the <body> on your payment page.Option 2 - NPM#
Install the package from npm.Then import it into your code using the following code.Add the following code to your applicationYou can collect user information as you wish. In this case we only need the email, so you can provide it directly if you already have it, or display an email field for the user to enter it.Once the email is obtained, request the token from Kushki to send it to your back-end as follows:The responsibility of the back-end is to receive the token obtained from your front-end and initiate the payment process with Kushki.When the user submits the form, your front-end transfers a token to an endpoint you have specified. With this token, you must make a call to our Webpay Plus authorization initiation endpoint, to initiate the payment and redirect the user.As a response to the call, you will get the redirect_url variable that you should use to redirect the user to the Webpay payment page to proceed with the payment.For the redirect, try not to use containers like Frame, Panel, or IFrame. Avoid functions such as pop-up windows as they may be blocked by the browser. Redirect the user in the same tab or window.
3. Capture the transaction#
Once the payment is completed, the client will be returned with a GET call to the return_url provided as a parameter in step 1. This call will be accompanied by a parameter called token located in the path, which represents the unique identifier of the transaction.For example, for return_url = "http://www.example.com/return the client will be returned to:GET http://www.example.com/return?token=020199203102301203where token is equal to 020199203102301203.According to the response you receive, show the user a success or failure screen to inform the customer if the subscription was created successfully or if there was an error.4. Kushki verifies authorization#
Kushki will validate the availability of funds with the card issuer. You can check the status of the transaction by making a call to the Get Status endpoint or via webhook. Once the response is obtained, save the ticketNumber as this will be the identifier for later capture, as well as a refund.5. Capture (Optional)#
Capture the amount you define according to the authorized by calling our capture endpoint, using the ticketNumber obtained in the authorization.5.1 Reversals or Refunds (Optional)#
Once an authorization has been made, it will not be possible to make a reversal of the separation of funds. If the reserved amount is not captured in the first 7 days, it will be automatically released on the seventh day.On the other hand, you will be able to make a refund of a charge already made, through this endpoint, within the first 7 days. If more than 7 days have passed since the capture, you must request a refund, which we will perform through the Transbank portal, up to 90 days.6. Test your integration#
There are test cards you can use in the UAT environment to make sure your integration is ready. Use them with any future expiration date.| Card | Number | CVV | Outcome |
|---|
| VISA | 4051 8856 0044 6623 | 123 | Generates approved transactions |
| AMEX | 3700 0000 0002 032 | 1234 | Generates approved transactions |
| MASTERCARD | 5186 0595 5959 0568 | 123 | Generates declined transactions |
| Redcompra | 4051 8842 3993 7763 | | Generates approved transactions |
| Redcompra | 4511 3466 6003 7060 | | Generates approved transactions |
| Redcompra | 5186 0085 4123 3829 | | Generates declined transactions |
| Prepago VISA | 4051 8860 0005 6590 | 123 | Generates approved transactions |
| Prepago MASTERCARD | 5186 1741 1062 9480 | 123 | Generates declined transactions |
When an authentication form appears with RUT and key, you must use the RUT 11.111.111-1 and the key 123.
