MIT Batch Authorization
POST/public/api/v1/mit/batch
Please review our rate limits before you begin your implementation.
Create multiple MIT (Merchant-Initiated Transaction) authorizations in a single request. Each entry mirrors the single MIT endpoint and is processed asynchronously, supporting partial success across the batch. Each transaction is processed individually, if the transaction passes initial validation then a transaction is created for background processing and a transaction is returned. If the initial validation fails, instead an error is returned. You will receive one callback for each individual transaction.
Use a MIT authorization when the customer has agreed to let the merchant charge them automatically. For example, monthly subscription payments must be handled using MIT. MIT is not suitable when the customer starts the payment themselves, like clicking a “Pay Now” button.
For more information about the differences between CIT (Customer-Initiated Transaction) and MIT, see our Core Concepts page.
All MIT transactions are processed asynchronously and cannot run in real time. Most are completed within a few seconds, but ePay does not guarantee processing times. Some payment methods, such as Vipps MobilePay, may take several days to complete, depending on the method’s processing rules.
If you want to offer your customers the ability to store their cards for faster checkout in the future, you must use CIT transactions. In such cases, you are required to provide a customerId when creating the payment. This ID links the stored card to the customer and enables quick-checkout functionality in future sessions.
Request
Responses
- 200
- 400
- 422
- 500
MIT batch accepted; returns per-entry creation results while processing continues asynchronously. Each transaction is processed individually, if the transaction passes initial validation then a transaction is created for background processing and a transaction is returned. If the initial validation fails, instead an error is returned.
Standard error response returned when a request fails. Contains a machine-readable error code, a human-readable message.
Standard error response returned when a request fails.
Contains a machine-readable error code, a human-readable message,
and an errors object with field-specific validation issues.
Standard error response returned when a request fails. Contains a machine-readable error code, a human-readable message.