| Error | Cause | Resolution |
|---|---|---|
| No active payment gateways configured. | Your configured payment gateway has not been activated. | Toggle the Gateway Status button from inactive to active for each of your configured payment gateways. |
| Paystack: Simulation Failed (Invalid API keys). | You provided invalid credentials or entered them in the wrong fields. | Ensure your public key is in the Public Key field, and your secret key is in the Secret Key field. Double-check that the credentials are copied correctly from your Paystack dashboard. |
| Flutterwave: Simulation Failed (Invalid authorization key). | You provided invalid credentials or entered them in the wrong fields. | Ensure your public key, secret key, and webhook secret are copied correctly from your Flutterwave dashboard and pasted into their respective fields. Save your changes before retrying the connection test. |
| Monnify: Simulation failed (Invalid authentication credentials). | You provided invalid credentials or entered them in the wrong fields. | Ensure your contract code, API key, and secret key are copied correctly from your Monnify dashboard and pasted into their respective fields. Save your changes before retrying the connection test. |
| Gateway simulation check required before activation. | You attempted to activate a gateway without running a connection test first. | Click the Test connection button and make a test or live payment to activate the gateway. |
Merchant payment.succeeded webhook must be delivered before activation. | You have not configured a webhook URL, or you have not generated a webhook secret after configuring the webhook URL. | Configure a publicly accessible webhook URL, then generate a webhook secret to receive and verify the payment.succeeded event before attempting activation. |
| No routing rule matched. | The paymentMethod field was not provided in the payment initiation request, or no routing rule is configured for that payment context. | Ensure you include the paymentMethod field in your payment initiation request. If the issue persists, check your smart routing rules to confirm a rule exists that matches the currency, payment method, and amount range of the transaction. If no rule matches, Archefusion falls back to the default provider order. |
| Webhook events not received in live mode. | Your webhook URL is not publicly accessible, or you have not generated a live webhook secret after configuring a webhook URL. | Use a publicly accessible server URL as your webhook URL, then click Get New Secret in Settings > API Keys > Webhooks to generate a live webhook secret. |
| Webhook signature verification failing. | The webhook signature does not match because the request body is being parsed before verification, the wrong secret is being used, or the base string is not constructed correctly. | Ensure your webhook route receives the raw request body before any JSON parsing middleware runs. Use your webhook secret, not your API secret key. Build the base string in the exact format timestamp.eventId.rawBody using the values from the x-archefusion-timestamp, x-archefusion-event-id, and raw body, then create an HMAC SHA256 hash and compare it to the x-archefusion-signature header value. |
Support
Troubleshooting
Solutions to common Archefusion integration errors including gateway activation issues, invalid credentials, routing mismatches, webhook delivery failures, and signature verification errors.
Was this page helpful?

