When verification finds inconsistencies in transaction amount, fees, or status, you can resolve them through a ticket-based workflow.

​
Scenarios

  • Automated reconciliation finds discrepancies that require manual review and handling
  • Customer service / operations manually flag exception transactions to follow up in the console

​
API Overview

  • POST /nps/ticket/tx: Create an exception transaction ticket (pass in transaction_id, the exception fields abnormals, and a description desc)
  • GET /nps/ticket: Query ticket details (status, exception fields, creation/update time)

​
Usage Flow

1

Create the ticket

For mismatched transactions, call POST /nps/ticket/tx and write the exception fields and description.
2

Track handling

Use GET /nps/ticket to check the ticket status and update time, and drive the handling through your internal processes.

​
Relationship with the Console

The API can be used together with the ticket module in the admin console: the console side is used for manual review and record keeping, while the API side is used for automated creation and querying.

Reconciliation and Verification APIs

First run statement queries and verifications, then create tickets for discrepancies.

API Authentication

View signature and authentication examples for a unified invocation method.