Skip to main content
POST
Verify payment

Authorizations

Authorization
string
header
required

Your secret key as a Bearer token. The key prefix selects the environment: sk_test_... (staging) or sk_live_... (production); a key on the wrong host is refused with 403 Unauthorized Access. Each key is limited to 10 requests per minute (429 beyond that) and, on production, to the IP addresses on your dashboard allowlist when one is configured.

Headers

customer-id
string
required

The merchant customer this request acts on behalf of.

Body

application/json
reference
string
required

The reference of the payment intent to submit for processing.

Example:

"99999533334"

otp
string

Confirmation OTP / transaction PIN. Required only when the transaction needs confirmation.

Example:

"123456"

Response

Payment intent submitted and processed.