Skip to main content

Card POS

Card-Present (POS) payments allow merchants to accept card payments through physical payment terminals at brick-and-mortar locations. These transactions require additional security information captured during the card-terminal interaction, including EMV chip data, Track2 data from magnetic stripes, and optional encrypted PIN blocks for online PIN verification. POS payments support traditional POS devices and software-only terminals (SoftPOS).

NetworksFeaturesIntegrationspayment_type
Visa, Mastercard
  • Server-to-Server
  • Checkout Page
  • Pay by Link
  • Payment Page Redirect
cardpos

Payment workflow​

The following diagram explains the Card POS payment workflow for the Server-to-Server integration.

Card POS — Server-to-Server
Payer (Cardholder)
POS Terminal
Merchant
OneAPI
Card Issuer
1. Presents card (chip/contactless/swipe)
2. Reads card data (EMV/Track2)
3. Create POS payment request (Payment API)
Request includes card data, EMV data, and terminal info
4. Authorization request
5. Authorization response
If online PIN is required (e.g. Single Tap), the response includes terminal_action: request_pin — prompt for PIN and retry with pin_block and sequence: subsequent
6. Payment result (success/declined)
Payment processing occurs asynchronously
7. Postback notification (payment status update)
8. Update order status in system
9. Display receipt

Scroll horizontally if the diagram is wider than your screen.

  1. 1
    Payer (Cardholder)POS Terminal

    1. Presents card (chip/contactless/swipe)

  2. 2
    POS TerminalPOS Terminal

    2. Reads card data (EMV/Track2)

  3. 3
    MerchantOneAPI

    3. Create POS payment request (Payment API)

  4. OneAPI

    Request includes card data, EMV data, and terminal info

  5. 4
    OneAPICard Issuer

    4. Authorization request

  6. 5
    Card IssuerOneAPI

    5. Authorization response

  7. OneAPI

    If online PIN is required (e.g. Single Tap), the response includes terminal_action: request_pin — prompt for PIN and retry with pin_block and sequence: subsequent

  8. 6
    OneAPIMerchant

    6. Payment result (success/declined)

  9. OneAPI

    Payment processing occurs asynchronously

  10. 7
    OneAPIMerchant

    7. Postback notification (payment status update)

  11. 8
    MerchantMerchant

    8. Update order status in system

  12. 9
    POS TerminalPayer (Cardholder)

    9. Display receipt

Integration options​

Choose how you want to accept Card POS:

Server-to-Server

Send card-present data from your POS or SoftPOS terminal to OneAPI via the Payment API, including EMV, Track2, and terminal information.
Start integrating
Last updated on