1. Two-steps Payments
Kushki Docs
English
  • Español
  • English
  • Home
  • Quick Start
    • Frequently Asked Questions
    • Moving to Production
    • Policy for Important API Changes
    • Test Data
    • Error Codes
    • Latest Features
  • Payment Glossary
    • Payments Glossary
  • One-time card payments (Online)
    • Supported card brands
    • Functionalities by business model
    • Network Tokens
    • One-step Payments
      • How do Card Payments Work?
      • Accept a Card Payment
      • Direct charge (without token)
      • Accept One-Time Payments with OTP
      • OTP Authentication Error Codes
      • Error codes for single card payments
    • Two-steps Payments
      • How do one-time payments with authorization and capture work?
      • Receive payments with authorization and capture
    • Refunds
      • Returns, cancellations, and refunds
    • 3DS Authentication
      • Introduction to 3DS
      • 3DS API integration
      • 3DS integration with kushki.js library
      • 3DS API integration plus kushki.js library
      • 3DS Error Codes
    • Apple Pay Payments
      • Apple Pay Configuration
      • Apple Pay Sandbox testing
  • Recurring Card Payments (Online)
    • Functionalities by business model
    • External subscriptions to Kushki
    • Authenticate your subscriptions with 3DS
    • Accept one-click payments with 3DS
    • Error codes in recurring charges
    • Scheduled payments
      • How do Credit or Debit Card Payment Recurring Charges Work?
      • Schedule a recurring charge
      • Manage your Scheduled Charges
    • OneClick Payments
      • Accepting One-Click Payments
      • How does authorization and capture work in OneClick payments?
      • Receive OneClick payments with authorization and capture
  • Card-present payments
    • Accept card present payments
    • Test data
    • Webhooks for card present
    • Raw card-present API
      • Raw card-present API overview
      • Cryptographic key exchange
      • Sample script to encrypt information
      • Take Payments
      • Frequently Asked Questions
      • Error codes for card-present transactions
    • Kushki One
      • First Steps
      • Autenticación y Cifrado de Requests
      • Accept payments with Kushki One
      • Amount Format
      • Async services and webhooks
      • Printing on SmartPOS terminal
      • Unified Error Catalog — Kushki ONE Connect
    • Kushki One Payment App
      • Overview
      • Process a payment
      • Split payment on the terminal
      • Refunds and PreAuth & Capture
      • Review Your Transactions
      • Terminal Setup
    • Transactions
      • Transactions
      • Cancel payments
  • Wire Transfers
    • Banks and transaction details for bank transfer payments
    • Receive Wire Transfers
    • Check the Status of a Transaction
    • Error Codes for Transfers
  • Cash Payments
    • How do Cash Payments Work?
    • Accept a Cash Payment
    • Authorized locations
    • Error Codes for declined cash transaction
  • Alternative payment methods (APM)
    • How do APM payments work?
    • Accept Bre-B payments
  • Money Disbursement
    • Payment Distribution
    • Recharge your balance for dispersions
    • Wire Transfer
      • How Does a Payment Distribution by Wire Transfer Work?
      • Payment Distribution to Bank Accounts
      • Disburse with Bre-B
      • Error codes for transfer dispersions
    • Cash
      • How does payment distribution in cash work?
      • Distribute Payments in Cash
      • Manage your Payment Distribution Transactions
  • Plugins
    • Shopify
      • Shopify
      • Plugin Operation
    • VTEX
      • VTEX Integration Guide
  • Payment Links
    • Smartlinks
  • Payment forms and buttons
    • Kajita
      • How Does it Work?
      • Payment Kajitas
    • Payment Button
      • Overview
      • Generate a payment button
  • Branch Offices Management
    • How to Onboard Submerchants via API
  • Notifications
    • Good Practices
    • Check your Webhooks
    • One-time Payments Webhooks
      • Webhook for One-Time Payments made with a card
      • Webhook for One-Time Payments by Wire Transfer
      • Webhook for One-Time Payments in Cash
    • Recurring Payments Webhooks
      • Webhook for Recurring Payments Made with Card
    • Payment Distribution Webhooks
      • Webhook for payment disbursement through wire transfer
      • Webhook for Payment Distribution in Cash
    • Payment button Webhooks
      • Webhooks with Payment Button
    • Smartlinks Webhooks
      • Webhooks with Smartlinks
    • Refunds Webhooks
      • Webhook for Voids and Refunds
      • Chargeback Webhooks
HomeMexico 🇲🇽Ecuador 🇪🇨Chile 🇨🇱Colombia 🇨🇴
Peru 🇵🇪
HomeMexico 🇲🇽Ecuador 🇪🇨Chile 🇨🇱Colombia 🇨🇴
Peru 🇵🇪
Status
Soporte / Support
English
  • Español
  • English
  1. Two-steps Payments

How do one-time payments with authorization and capture work?

Learn about the authorization and capture process, through which you can authorize an amount from your client's card and charge when the service has been completed.
This functionality is available for the following models:
☑ Acquirer

☐ Aggregator
Receiving one-time card payments under the authorization and capture, involves reseiving funds from your customer’s card, allowing executing the capture of funds once the service is completed. It also allows reaothorizations to extend the validity of the funds or change the initial amount.
Product in beta version 🔐👨‍💻
We are working on our beta version. Stay tuned for its official release! You can also contact your account manager for more information.

Operation Details#

Important
Keep in mind that the validity of the authorization may vary depending on the commercial negotiation.
ParticularityDetails
Supported card typesVisa and Mastercard debit and credit cards
Authorization duration7 days for debit cards and 28 days for credit cards.
Authorization end time7 days or 28 days from the time the authorization is generated
Reauthorization amountCan be higher or lower than the authorization amount. There is not maximum limit
Capture amountThe 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
Number of capturesOnly 1 capture per authorization is allowed
Cancellation of authorization before the expiration dateRecommended, using the void endpoint
Cardholder limit restoration upon cancellationTThe limit depends on the issuer to be restored
Cardholder limit restoration upon authorization validity expirationThe limit is immediately restored

Stages of the process#

Authorization and capture(also called two-step payment), consist of two stages: Authorizations of the amount and capture or release of funds
Autorización y captura para pagos únicos en Colombia

Authorization#

1. Selection of payment method#

On your website or app, the user selects a card as the payment method and provides the card details to be used for payment.

2. Sending data to Kushki#

The merchant collects the data, sends it to Kushki, and requests a unique authorization payment token.

3. Sending the token#

Kushki receives the data and sends you the unique authorization payment token.

4. Authorization of the amount#

The merchant requests Kushki to authorize the customer’s card amount.

5. Verification of funds#

Kuhski processes the authorization with the issuer, verifying the availability of funds. If this process is successful, it retains that amount on the customer’s card to guarantee it to the merchant.

6. Notification#

Kushki returns a response regarding the authorization process.

Reauthorization#

If you wish to modify the validity period of the authorization or the value of the amount, you can request a reauthorization. Keep in mind that each reauthorization adds to the value of the initial authorizations. The total sum of the initial authorization plus any subsequent reauthorizations will be the maximum amount that can be captured.

Capture or release of funds#

1. Execution of the charge#

Once you have authorized the amount on your customer’s card, you can request the collection or release of the authorized balance.

2. Translation status notification#

At this stage, you will be notified of the transaction status. You can receive these notifications through a webhook that you expose for Kushki to consume. You also have access to the Kushki console to verify transitions along with the details of each and their status.

Receive payments with authorization and capture
Learn how to integrate the receipt of one-time card payments through the authorization and capture scheme.
Modificado en 2026-10-14 19:54:21
Anterior
Two-steps Payments
Siguiente
Receive payments with authorization and capture
Built with