Batch MIT Transaction Management API
Please refer to Payment Scenarios - Batch MIT get more details.
Create batch MIT transaction
file_url is a required parameter. It must be a complete, publicly accessible URL on the internet. For the specific protocol, please refer to the file format documentation.
Query batch MIT transaction by ID
After an MIT Batch Transaction is created, you can query its processing details via the Query Batch MIT Transactions By ID API.
Query batch MIT transaction by search
You can use the Query Batch MIT Transactions By Search API to search for a specific transaction or transactions within a certain time range.
POST
Create Batch Transaction
>POST
Query Batch Transactions By ID
>POST
Query Batch Transactions By Search
>File Format
| Parameter | Required | Description |
|---|---|---|
| Action | Yes | Type of operation. Supported values (lowercase only): authorize / payment / void / cancellation / refund |
| Reference Number | No | Merchant-side order reference number |
| Original Transaction ID | Conditionally Required | Original transaction ID: Not required when Action = authorize, must be provided when Action = void / refund |
| Customer UUID | No | Unique customer identifier |
| Amount | Yes | Transaction amount. The unit is subject to the interface agreement. |
| Token ID | Conditionally Required | Card token. Either Token ID or Card Number is required (mutually exclusive). |
| Card Number | Conditionally Required | Card number. Either Card Number or Token ID is required (mutually exclusive). |
| Expiry Month | Conditionally Required | Card expiration month (MM format). Required if Card Number is provided. |
| Expiry Year | Conditionally Required | Card expiration year (YY format, e.g., 25 represents 2025). Required if Card Number is provided. |
| CVC | No | Card verification code |
| Remark | No | Remarks/notes information |