1. Kushki One Payment App
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
    • Apple Pay for Subscriptions
    • Scheduled payments
      • How do Credit or Debit Card Payment Recurring Charges Work?
      • Create 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
    • Transactions
      • Transactions
      • Cancel payments
    • 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
  • Wire Transfers
    • Shopping experiences and transaction details for bank transfer payments
    • Receive Wire Transfers
    • Check the Status of a Transaction
  • Cash Payments
    • Accept a Cash Payment
    • Authorized locations
    • Error Codes for declined cash transaction
  • Alternative payment methods (APM)
    • How do APM payments work?
    • Accept Yape payments
  • Money Disbursement
    • Wire Transfer
      • How does the disbursement through bank transfer work?
      • Payment disbursement to bank accounts
      • Error codes for transfer disbursements
    • Card
      • How does sending funds to cards work?
      • Send money to a card
      • Error Codes
  • 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 card disbursement
    • 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. Kushki One Payment App

Process a payment

Accept card payments in semi-integrated mode from your SmartPOS terminal
🚧 Early Release — Beta
This product is in early access. Parameters, response structures and behaviors may change without prior notice. Do not use this version in production without coordinating with the Kushki integrations team first.
This is the cashier's main flow. From the Home tab you pick the Sale operation, enter the amount, the customer picks how to pay and the terminal handles the entire authorization on its own, with no extra action needed from the merchant's system.
Is the check being split between several people?
Use the Split Payment operation instead of Sale. It divides the total into several consecutive payments, each with its own card.

Before you start#

Check this first
The terminal powered on and connected to the network.
The cashier signed in with their personal user.
If no users have been created yet, see User management.

Step 1 — Enter the amount#

From the Home tab, tap Sale in the operations menu. The terminal shows the numeric keypad with a Sale header. Enter the transaction amount and tap the confirmation button, the blue check icon.
Amount entry screen in the app
The amount is entered in your terminal's currency
Kushki configures the currency per terminal during activation. The app applies it automatically, with the number of decimals that matches your country.

Step 2 — Tip#

Conditional step
This appears only if the merchant account has tips enabled. If it does not apply, the app jumps straight to Step 3. The available options are defined in Tip settings.
The terminal shows the customer the Add Tip? screen. The customer picks one of the preconfigured options, selects Custom to enter a free value, or taps No Tip.
Tip selection screen
The tip is added to the subtotal to form the total charged to the card, and it is recorded as a separate field on the receipt.

Step 3 — Installment selection#

Conditional step
This appears only if your merchant account has installments enabled and the amount is above the configured threshold. If it does not apply, the app jumps straight to Step 4.
The app shows the Installment options screen. The customer or the cashier picks between:
OptionDescription
Pay in FullCharges the whole amount in a single transaction. Selected by default
X installmentsSplits the amount into installments, based on the options enabled for your merchant and the card issuer. The app calculates and shows the value of each one
Installment options screen
Tap Confirm to continue.

Step 4 — Card presentation#

The terminal shows the card-waiting screen with the confirmed amount and three entry methods. The customer presents their card however they prefer.
MethodDescription
Contactless (NFC)The customer taps the card or device on the reader. The fastest method
ChipThe customer inserts the card into the slot at the bottom of the terminal
Magnetic stripeThe customer swipes the card through the stripe reader. Available as a fallback
Card-waiting screen
The cashier can cancel the transaction at any point from this screen by tapping Cancel Sale.
This screen is not localized yet
In the current terminal version, the card-waiting screen keeps its labels in English even when the interface is set to Spanish: Ready when you are, Tap, Insert, Swipe, Cancel Sale and Included tip. The amount also appears without a thousands separator.

Step 5 — Digital signature#

Conditional step
This applies only to certain credit card transactions, according to the issuing bank's rules. Not every transaction requires it.
The terminal asks the customer to sign on the touchscreen. The customer signs with a finger or a stylus and taps Confirm. To start over, they use Clear and sign again.
Digital signature screen

Step 6 — Processing#

While the terminal talks to the card network, the waiting screen appears with the amount in progress. This step usually takes 2 to 5 seconds with good connectivity.
Processing screen

Step 7 — Result#

Approved#

If the authorization succeeds, the app shows the Approved screen with a "charged successfully" message and generates the receipt automatically.
Approved transaction screen
From this screen the cashier has three options for the receipt:
ActionDescription
EMAILSends the receipt by email to the customer or to the merchant's record
PAYLOVESends the receipt to the customer's loyalty program, if your merchant account has it enabled
SKIPCloses the flow with no digital delivery. The transaction is still recorded in the Sales List
The Print button at the bottom produces the physical receipt on the built-in printer.
The Ticket # is the transaction reference
The 18-digit Ticket # shown on the Approved screen identifies the transaction both on the terminal and in the Kushki portal. Share it with the customer if they need to follow up later.

Declined#

If the authorization fails, the terminal shows the Declined screen with the reason, when the processor provides one. The transaction is recorded in the Sales List with a Declined status and no Ticket # assigned.
What to do about a decline:
1.
Check that the card has sufficient funds and is not blocked.
2.
Try a different entry method. If contactless failed, try chip.
3.
If the problem persists, ask the customer for another card.
Refunds and Auth & Capture
Learn how to process refunds and manage pre-authorizations from the terminal.
Terminal settings
Adjust installments, tips, users and receipts to fit your merchant account.
Modificado en 2026-10-19 14:46:43
Anterior
Overview
Siguiente
Split payment on the terminal
Built with