Accept card payments at physical retail locations using Dintero terminals. You create a checkout session that targets a specific terminal, and the customer taps, inserts, or swipes their card to pay. In-person payments reuse the same Checkout API, session profiles, and transaction management you already use for online payments. The only difference is that the session references a store and terminal.Documentation Index
Fetch the complete documentation index at: https://docs.dintero.com/llms.txt
Use this file to discover all available pages before exploring further.
Integration steps
Set up your account for in-person payments
Contact Dintero to enable In-Person Payments on your account. You need a payout destination (the merchant entity that receives funds) with completed KYC verification.See Terminal onboarding for the full setup process.
Register a store and terminal
In Backoffice, create a store linked to your payout destination, then register a terminal to the store. Each terminal gets a unique ID that you reference when creating sessions.You’ll need three identifiers for every terminal payment:
| Identifier | What it is |
|---|---|
payout_destination_id | The merchant entity receiving funds |
store.id | The physical store location |
terminal_id | The specific payment terminal |
Create a payment profile
Create a payment profile with Seitatech In-Person Payments as the only enabled payment method. Terminal sessions must have
seitatech.in_person as the sole payment type.Create a terminal session
Send a
POST to /v1/sessions-profile with the order details and the store/terminal identifiers. The payment is triggered on the terminal as soon as the session is created. There is no hosted checkout page.Include order.store.id, order.store.terminal_id, and order.store.payout_destination_id in your request, and reference your in-person payment profile with profile_id.See Create a terminal session for the full payload.Customer pays on the terminal
The terminal prompts the customer to tap, insert, or swipe their card. Dintero auto-captures terminal payments by default, so the transaction moves directly to
CAPTURED on success.Handle the result
Receive the transaction result via your
callback_url and webhooks. Manage refunds and voids through the standard Transactions API, just like online payments.What’s next
In-person overview
Detailed overview of how terminal payments work.
Terminal onboarding
Set up payout destinations, stores, and terminals.
Create a terminal session
Full payload reference and response handling.