Skip to main content
POST
Create a terminal payment
If you have a v1/terminal-payments webhook subscription, you will receive the payment outcome (authorized or refused) as a webhook event once the cardholder completes the payment on the terminal.

Authorizations

Authorization
string
header
required

Bearer authorization header: Bearer <token>, where <token> is the access token received from the authorization server at the end of the OAuth 2.0 flow.

Headers

X-Qonto-Idempotency-Key
string
required

Learn more in Idempotent Requests.

Example:

"123e4567-e89b-12d3-a456-426614174000"

X-Qonto-Staging-Token
string

Required only for Sandbox API requests; to get one, please sign up to the Developer Portal.

Path Parameters

id
string<uuid>
required

Terminal UUID (from GET /v2/terminals).

Body

application/json
amount
object
required
metadata
object

Optional free-form JSON object. Must be a valid JSON object and must not exceed 1kB. Stored as-is and echoed back in the 202 response. Use it to cross-reference the payment with your own system — for example an order ID, table number, or any other POS-specific data. The content is not interpreted by Qonto.

Example:

Response

The payment has been accepted and is being processed asynchronously.

terminal_payment
object
required