Skip to main content
POST
Confirm a PayIn in sandbox
Force a pending PayIn to APPROVED, REJECTED, or EXPIRED in staging or UAT. TumiPay then sends the merchant webhook. See Sandbox Confirm for supported methods, identifiers, and prerequisites.
Not available in production. Calls return 404 NOT_FOUND.
cURL

Authorizations

Token-Top
string
header
required
Authorization
string
header
required

Basic authentication header of the form Basic <encoded-value>, where <encoded-value> is the base64-encoded string username:password.

Body

application/json
transaction_id
string
required

TumiPay ticket, merchant reference, or external reference that belongs to the authenticated merchant.

Example:

"xiK9LSjwFyBYYRG"

payment_method
string
required

Payment method enum name in uppercase (e.g. SPEI, BREB, BANK_TRANSFER). Do not use the portal label.

Example:

"SPEI"

status
enum<string>
required

Target status. Not every method supports every status.

Available options:
APPROVED,
REJECTED,
EXPIRED
Example:

"APPROVED"

Response

Transaction confirmed

code
string
Example:

"01"

status
string
Example:

"SUCCESS"

message
string
Example:

"Transacción confirmada"

data
object