API Explorer

:::warning Rate limits Please review our <a href="/guides/rate-limits">rate limits</a> 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. You’ll receive the outcome of each payment on the `notificationUrl` you provide within the request, making it the primary way to track the result of these payments. [Webhooks](/api/webhooks/create-webhook) can be used separately if you need broader, system-wide updates. 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 <a href="/get-started/core-concepts">Core Concepts</a> page. All MIT transactions are processed <b>asynchronously</b> 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. When you match the returned transaction results back to your original batch request, the transaction order is preserved from request to response. This means you can always correlate each result to the original request item by using the array index. You can also provide a `reference` on each transaction in your request. When present, the same `reference` value is included in the returned result for that transaction, which gives you an explicit way to link results back to your own records. If you choose to rely on `reference` for correlation, make sure you send `transaction.reference` for every transaction in the batch. Otherwise, use the array index as the correlation key. 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 <code>customerId</code> when creating the payment. This ID links the stored card to the customer and enables quick-checkout functionality in future sessions. *We recommend a minimum timeout of 10 seconds.*