Skip to main content
The method Archefusion uses to calculate the waiting time between retry attempts when a gateway is unresponsive.
The initial waiting time in milliseconds before Archefusion retries a failed gateway attempt.
The order Archefusion uses to route a payment across your available gateways when no smart routing rule matches the transaction. See smart routing to configure your rules.
The automatic process of routing a payment to the next available fallback gateway when the first configured gateway is unavailable or unresponsive.
The next gateway in your smart routing rule that Archefusion routes to when the first configured gateway is unavailable or unresponsive, so a single gateway outage doesn’t fail the payment. See smart routing to configure the order.
A connection test that verifies your gateway credentials are valid and that Archefusion can successfully connect to your gateway account.
A small random delay added to retry attempts to prevent multiple concurrent transactions from hitting the same gateway at exactly the same time during high-traffic periods.
The verification process Archefusion uses to confirm the legitimacy of a merchant’s business before granting access to live mode.
The additional time added to a transaction by Archefusion’s routing process, including any retries or failover attempts.
Real-time information about the availability and performance of each configured payment gateway. Archefusion uses this data alongside your routing rules to determine the best gateway for each transaction.
The operational mode in which Archefusion processes real payments using live API keys and live gateway credentials.
The maximum waiting time in milliseconds between retry attempts, regardless of what the backoff strategy calculates. This caps the delay so retries do not wait indefinitely between attempts.
The maximum number of times Archefusion will retry a payment on a single gateway before moving to the next one in your failover strategy.
Businesses or individuals who use Archefusion to route payments through multiple payment gateways.
A refund for an amount less than the original transaction amount. For example, refunding ₦200 on a ₦500 transaction.
A service that processes payments between a customer and a merchant. Examples include Paystack, Flutterwave, and Interswitch.
The process of managing and routing payments across multiple payment gateways through a single integration. Archefusion acts as a payment orchestrator, selecting the best gateway for each transaction based on routing rules and live provider health data.
The URL a customer is sent to after completing payment on the gateway checkout page.
The process of returning funds to a customer after a successful payment
The number of times Archefusion attempts to process a payment on a gateway before moving to the next one.
Archefusion’s automatic rule-based system that selects the best payment gateway for each transaction.
The improvement in transaction success rate achieved by Archefusion’s smart routing, compared to what the success rate would have been without routing.
The operational mode in which Archefusion processes simulated payments using test API keys and test gateway credentials.
The maximum time in milliseconds Archefusion waits for a gateway to respond before marking the attempt as failed and moving to the next retry or failover gateway.
An HTTP POST request that Archefusion sends to your server URL when an event occurs, such as a payment succeeding or failing.