Confirms a previously created transaction and finalizes it for processing.
Confirms a transaction that was created with a funding type that requires explicit confirmation (e.g., cash, debit card).
Use this endpoint after a transaction has been created and the payment has been collected or authorized:
- Cash transactions: after the cash has been received at the branch
- Debit card transactions: after the card payment has been approved (requires
last4CardNumberandapprovalCode)
- Validates the transaction exists and belongs to the branch
- Releases any compliance holds (Hold 87)
- For debit card funding, registers the card payment details
- Updates transaction status to CONFIRMED in DynamoDB
- Generates and returns the transaction receipt
Requires x-client-id and x-secret-key headers.
- If the transaction was already confirmed, returns the existing receipt without re-processing.
- Transactions with funding type
U(undefined) orH(hold/remote) cannot be confirmed through this endpoint.
400Validation errors, invalid branchId, missing debit card fields401Invalid credentials404Transaction not found422Transaction not eligible for confirmation500Internal error
Unique identifier assigned to the integrating client. It determines the validation rules, allowed values, compliance policies, and operational limits applied to the request.
Error codes: required=400001, type=400002, minLength=400003, maxLength=400004
Unique identifier of the transaction.
Error codes: required=400001, type=400002, minLength=400003, maxLength=400004
Output format for the receipt generated after confirmation. Supported values: html (default) or pdf.
Error codes: type=400002, minLength=400003, maxLength=400004, allowedValues=400010
Represents the financial, operational, and processing configuration of the transaction.
Contains all parameters required to calculate, validate, route, and execute the transfer, including amounts, currencies, delivery method, funding source, fees, and payout instructions.
All fields are validated against business rules, compliance policies, and operational constraints before the transaction is accepted for processing.
Error codes: type=400002
- Confirm cash transaction
- Confirm debit card transaction
curl -i -X POST \
https://sandbox-viablocks.viamericas.io/transaction/confirm \
-H 'Content-Type: application/json' \
-H 'x-client-id: string' \
-H 'x-secret-key: string' \
-d '{
"uuid": "eddcf7fb-d2ab-4f4b-9d04-3799304f773c",
"transactionContext": {
"branchId": "A00765",
"cashierId": "TEST.T"
},
"receiptFormat": "html"
}'Response success
- Transaction confirmed successfully
- Transaction was already confirmed (idempotent)
{ "status": "success", "message": "The transaction has been confirmed.", "folio": "123456789", "transaction_id": "A00765-8", "receipt_url": "https://s3.viamericas.io/receipts/eddcf7fb-d2ab-4f4b.html", "receipt_html": "<div style=\"font-family:monospace\">VIAMERICAS CORP...</div>" }