> ## Documentation Index
> Fetch the complete documentation index at: https://docs.archefusion.com/llms.txt
> Use this file to discover all available pages before exploring further.

# FAQs

> Get answers to your questions about Archefusion, covering everything from onboarding and payment configurations to smart routing, webhooks, and account management.

## Onboarding

<Accordion title="1: How do I access the Archefusion dashboard?">
  Navigate to the [Archefusion sign-in](https://app.archefusion.com/sign-in) page, enter your email address, password, and OTP sent to your inbox. Upon successful verification, you should be able to access your dashboard. If you face any issues, contact our support team at [support@archefusion.com](mailto:support@archefusion.com).
</Accordion>

<Accordion title="2: What documents are required to complete the onboarding process?">
  To complete the onboarding process, you are required to provide your business registration documents for KYB. For more information, visit the [KYB verification](https://docs.archefusion.com/pages/kyb-verification) page.
</Accordion>

<Accordion title="3: How long does the verification typically take?">
  Archefusion’s business verification typically takes 24-48 hours. If you have any verification issues, contact the Archefusion support team.
</Accordion>

<Accordion title="4: What happens if my verification is rejected?">
  You will receive a notification on your Archefusion dashboard and email stating why your verification was rejected. You can then correct your documents and resubmit for verification.
</Accordion>

<Accordion title="5: How do I get access to live mode?">
  You will get access to live mode once your KYB verification is approved and your payment gateway is configured.
</Accordion>

<Accordion title="6: Can I start integrating while waiting for verification?">
  Yes, you can start integrating in test mode, and once your verification is complete, you can switch to live mode.
</Accordion>

## API keys

<Accordion title="7: How do I generate a new API key if I lost my previous one or it was compromised?">
  Navigate to "Settings" > "API Keys." Click the three dots next to your current API key and select "Revoke Key" to invalidate the old one. Then click "Create New Key" to generate a new one.
</Accordion>

## Payment configurations

<Accordion title="8: How many payment gateways can I integrate?">
  It depends on your pricing plan. Visit the [pricing page](https://www.archefusion.com/pricing) to know the gateway limit for your plan.
</Accordion>

<Accordion title="9: What payment gateways does Archefusion support?">
  Archefusion supports a wide range of payment gateways, including Paystack, Flutterwave, Interswitch, and more. For a comprehensive list of supported gateways, visit the [supported gateways and payment methods page](https://docs.archefusion.com/pages/supported-gateways-and-payment-methods).
</Accordion>

<Accordion title="10: Why do I have to provide my gateway credentials?">
  Archefusion is a payment orchestrator; therefore, you have to provide your gateway credentials so it can connect to your gateway accounts and route payments through them on your behalf.
</Accordion>

<Accordion title="11: Are my gateway credentials safe?">
  Yes, Archefusion securely encrypts your gateway credentials.
</Accordion>

<Accordion title="12: How do I integrate multiple gateways with Archefusion?">
  Configure each payment gateway you want to integrate in the Archefusion dashboard, then set your smart routing rules. For a detailed guide, visit the [payment gateway](https://docs.archefusion.com/pages/payment-gateway) page.
</Accordion>

<Accordion title="13: What happens if a payment gateway I configured goes down?">
  If a payment gateway you configured goes down when a customer attempts to make a payment, Archefusion routes the payment to the next available fallback gateway in your smart routing rule.
</Accordion>

<Accordion title="14: What happens if all configured gateways fail?">
  This is an extremely rare situation, as you can configure and route payments to multiple payment gateways as fallbacks. However, if all gateways fail, then the payment will not go through.
</Accordion>

<Accordion title="15: I am unable to activate a payment gateway. What should I do?">
  Ensure you have configured a publicly accessible webhook URL and generated a webhook secret. Then, test the simulated payment flow and ensure it succeeds. This will automatically activate the gateway.
</Accordion>

## Smart routing and payments

<Accordion title="16: How does smart routing work in Archefusion?">
  Smart routing is Archefusion's automatic rule-based system that decides which payment gateway processes a transaction. When a customer initiates a payment on your platform, Archefusion evaluates your predefined routing rules and live provider health data to determine the best gateway, then routes the payment accordingly without any manual intervention.
</Accordion>

<Accordion title="17: How does Archefusion select the best payment gateway to process a payment?">
  Archefusion selects the best gateway by evaluating your smart routing rules in order of priority, starting with the lowest priority number. It checks the conditions defined in each rule, such as currency, payment method, and transaction amount range, alongside live provider health data to determine the most suitable gateway for that transaction.
</Accordion>

<Accordion title="18: How do I set my smart routing rules?">
  Log in to your merchant account on Archefusion, navigate to “Payment Gateways” > “Smart Routing” and set your routing rules. For a detailed guide, visit the [smart routing page](https://docs.archefusion.com/pages/smart-routing).
</Accordion>

<Accordion title="19: Can I set a preferred gateway for specific transaction types?">
  Yes. For example, you can set Flutterwave as the primary gateway to process card payments within the range of ₦20,000 to ₦50,000.
</Accordion>

<Accordion title="20: Do I have to set up rules for each payment I want to receive?">
  Yes, you have to set up a routing rule for each payment scenario you want to handle, defined by conditions such as currency, payment method, and transaction amount range. However, you can set these rules directly in the smart routing section without writing a line of code.
</Accordion>

<Accordion title="21: How does Archefusion reduce payment failures?">
  Archefusion reduces payment failures in two ways. First, it routes each transaction to the best available gateway upfront based on your routing rules and live provider health data. Second, if a gateway is unavailable or unresponsive during routing, it automatically retries the transaction on the next available fallback gateway based on your [failover strategy](https://docs.archefusion.com/pages/glossary#failover).
</Accordion>

<Accordion title="22: How do I know if Archefusion is really reducing payment failures?">
  Log in to your merchant account on Archefusion, navigate to “Observatory” > “Routing Insights”, and check the success lift tab. This shows you how smart routing has improved the transaction success rate compared to what it would have been without it. It also shows the number of failed payments prevented.
</Accordion>

<Accordion title="23: Will my customers be delayed if Archefusion retries a failed payment?">
  No, payment retries typically happen within seconds, so your customers experience little to no delay.
</Accordion>

<Accordion title="24: What happens if a payment fails?">
  It depends on when the failure occurs. If a gateway is unavailable or unresponsive during routing, Archefusion automatically skips it and routes the payment to the next available gateway based on your failover strategy, so your customer is redirected to a working checkout page. However, if a payment fails on the checkout page, for example due to a declined card or insufficient funds, the transaction is marked as failed. This is outside Archefusion's control.
</Accordion>

<Accordion title="25: Does Archefusion hold my money during the payment process?">
  No, Archefusion does not hold funds at any point in the payment process. It simply routes the transaction to the appropriate payment gateway and keeps a record of it.
</Accordion>

<Accordion title="26: How can I view my transactions on the dashboard?">
  Log in to your [merchant account](https://app.archefusion.com/sign-in) on Archefusion, navigate to "Transactions," and view all your transactions in a unified table. You can filter by payment method, status, date range, and gateway to find specific transactions.
</Accordion>

<Accordion title="27: What's the difference between merchantOrderId, paymentId, and the gateway reference?">
  `merchantOrderId` is your own order reference, generated by your system to track and reconcile a payment on your side. `paymentId` is Archefusion's identifier for the payment; use it to verify a payment or check its status through Archefusion. The gateway's own transaction reference is managed by Archefusion internally and is not something you set. For a full breakdown, visit the [payment identifiers](https://docs.archefusion.com/pages/developer-resources/payment-identifiers) page.
</Accordion>

<Accordion title="28: What payment method does Archefusion support?">
  Archefusion currently supports card and transfer payments. Once a customer is routed to a gateway, they can also pay using any method that the gateway supports at checkout, such as USSD, bank transfer, mobile Money, or QR payments.
  For a full list of supported payment methods per gateway, visit the [supported gateways and payment methods](https://docs.archefusion.com/pages/supported-gateways-and-payment-methods) page.
</Accordion>

<Accordion title="29: How do I accept real payments?">
  Switch to live mode by replacing your test API keys with your live secret keys, updating your gateway credentials to live, and toggling the Live button in your Archefusion merchant account. For a detailed guide, visit the [go-live page](https://docs.archefusion.com/pages/go-live).
</Accordion>

<Accordion title="30: A customer says they paid but didn't receive value. How do I reconcile?">
  Find the order in your own records and use the merchantOrderId you stored at initiation to locate it, then [verify the payment's status](https://docs.archefusion.com/pages/accept-payments#verify-transaction) with Archefusion. This is why storing your merchantOrderId against every order matters; it lets you reconcile any payment from your own system. See [payment identifiers](https://docs.archefusion.com/pages/developer-resources/payment-identifiers).
</Accordion>

## Webhooks

<Accordion title="31: Why am I not receiving webhook events?">
  Common reasons are: you haven’t added the Archefusion webhook URL to your gateway dashboard, you provided a webhook URL that isn’t publicly accessible, or a webhook secret hasn’t been generated. See [Webhook setup](https://docs.archefusion.com/pages/webhook-setup#step-1-paste-the-archefusion-webhook-url-for-each-gateway-into-your-gateway-accounts) to properly configure your webhook.
</Accordion>

<Accordion title="32: Do I need to set up a webhook URL for each payment gateway I integrate with?">
  No. You just need to paste the Archefusion-generated webhook URL into each of your gateway accounts so Archefusion can receive payment notifications from those gateways. Then you register one webhook URL with Archefusion to receive all payment event notifications on your server, regardless of how many gateways you have configured.
</Accordion>

<Accordion title="33: How do I verify a webhook is actually from Archefusion?">
  Every webhook event from Archefusion includes an `x-archefusion-signature` header. To verify it, build a base string using the timestamp, event ID, and raw request body in the format `timestamp.eventId.rawBody`, then create an HMAC SHA256 hash of that string using your webhook secret. If the hash matches the signature in the header, the event is genuinely from Archefusion.
  For a detailed guide and code example, visit the [handle webhook notifications](https://docs.archefusion.com/pages/handle-webhook) page.
</Accordion>

<Accordion title="34: What's the difference between a Webhook URL and a Callback/Redirect URL?">
  A webhook URL is your server endpoint that receives automated payment event notifications from Archefusion. It runs server-side and is used to update your database and trigger business logic. A redirect URL is where your customer is sent after completing or abandoning payment on the gateway checkout page. Both serve different purposes and are configured separately.
</Accordion>

## Account management

<Accordion title="35: Do I have to provide my business details for each merchant account I create?">
  Yes, you have to provide different business details for each merchant account you create.
</Accordion>

<Accordion title="36: Can I change a team member's role after inviting them?">
  Yes, you can change a team member's role after inviting them.
</Accordion>

## Support

<Accordion title="37: How do I contact support?">
  You can contact our support team by sending an email to [support@archefusion.com](mailto:support@archefusion.com).
</Accordion>