API Explorer

:::warning Batching and Rate limits ePay strongly recommends merchants to implement the **<a href="/api/mit-batch-authorization">MIT Batch Authorization</a>** endpoint over the single MIT authorization endpoint. Please review our <a href="/guides/rate-limits">rate limits</a> before you begin your implementation. ::: A MIT (Merchant-Initiated Transaction) is a payment initiated by the merchant, typically based on a previously established agreement, such as a subscription. You’ll receive the outcome of the payment on the `notificationUrl` you provide within the request, making it the primary way to track the result of this payment. [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. 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 5 seconds.*