Receive one-click payments with authorization and capture

Separate the authorization and capture on subscribed cards to create a charge now and capture funds later

Web

Android

iOS

This functionality is available for the following models:

☑ Acquirer

☐ Aggregator

Receive OneClick payments using the authorization and capture scheme enable secure storage of your customer's card data, guaranteeing fund availability on the customer's card for a maximum of 7 days for debit cards and 28 days for credit cards. If the payment is not captured at that time, the held funds will be released by the issuing bank back to the cardholder.

Important

Please note that due to our risk policies, available payment methods and integration types may vary when you formalize the affiliation. We will inform you on how to proceed if this process applies to your merchant.

Flow

The flow you will integrate will be as follows:

1. Create card enrollment

The first step in generating OneClick payments with the authorization and capture scheme is to enroll your customer's card. To perform the enrollment, follow the instructions given in the relevant article Generate one click payments.

If the subscription is successful, you will receive thesubscriptionId.
The next step will be to make an authorization request from your back-end and then proceed with capture or unsubscription requests as needed, depending on the case.

2. Authorize the charge

With the subscriptionId of your card received in the previous step, you will need to make a call to our authorization endpoint to initiate the reservation of a given amount.

JavaScript

Python

PHP

You can get more information in our API reference.

3. Kushki verifies authorization

Kushki will validate the availability of funds with the card issuer.
Once you have received Kushki's response, save theticketNumber as this will be the identifier for later capture as well as cancellation.

4. Capture or release funds

4.1. Performs capture (Optional)

Important

The maximum amount to be captured may be 10% higher than the total amount of the initial authorization plus the n reauthorizations that may be executed.

Once you are required to collect the funds from the card, capture the amount you define according to the authorized by calling our capture endpoint for subscriptions OneClick, using the subscriptionId of the card and ticketNumber obtained in the authorization.

JavaScript

Python

PHP

You can find more information in our API reference.

4.2. Void authorization (optional)

If you need to void an authorization for funds to be released to the cardholder, you can do so by calling our void of collections enpoint, using the ticketNumber obtained in the authorization.

Once the authorization has been voided, it may take up to 30 days for the balance to be reflected back in the cardholder's account.

JavaScript

Python

PHP

You can find more information in our API reference.

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 CVV, zip code and future expiration date.

Approved Transaction: 5451951574925480

Declined transaction on token request (front-end): 4574441215190335

Transaction declined on authorization: 4349003000047015

Transaction declined on capture: 4547004841271012

Prepare Your Certification

Take into consideration the following guidelines to pass the technical certification (required to obtain production credentials):

Tax calculations are correct.

Do not store sensitive card data in your database (full card number, CVV, etc.).

On-screen messages according to Kushki responses.

Save and record all Kushki responses (required in case support is needed).

The Kushki logo must be visible to the customer. You can find our logo in various formats here.

Make sure you submit all the required data specified in the API reference.

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

The cardholder's name is required.

The card number field is required.

The card number field accepts only numbers.

The card number field accepts a maximum of 16 digits (may be fewer).

The CVV field is required

The CVV field accepts only numbers.

The CVV field allows a maximum of 4 digits and a minimum of 3.

The CVV field must be of password type.

The expiration date is required.

The expiration date must accept only future dates.

The payment button is disabled after the first click.

The Kushki logo must be visible to the customer. You can find our logo in various formats here.
-Make sure to send your customer-payer's contact information (contactDetails), along with the billing ( orderDetails -> billingDetails)and shipping information (if your business model requires it: orderDetails -> shippingDetails),within the request to make the charge. You can find an example of the JSON Body for the charge in API reference.

Receive one-click payments with authorization and capture

Flow#

1. Create card enrollment#

2. Authorize the charge#

3. Kushki verifies authorization#

4. Capture or release funds#

4.1. Performs capture (Optional)#

4.2. Void authorization (optional)#

Test your integration#

Prepare Your Certification#

Flow

1. Create card enrollment

2. Authorize the charge

3. Kushki verifies authorization

4. Capture or release funds

4.1. Performs capture (Optional)

4.2. Void authorization (optional)

Test your integration

Prepare Your Certification