| Field | Type | Description |
|---|---|---|
| success | Boolean | Indicates the status of the request. |
| statusCode | Number | Indicates the outcome of the request. |
| message | String | Indicates the reason why the request failed. |
| data | Object | Contains additional details about the reason why the request failed. |
Error types
Amount must be a number conforming to the specified constraints
Amount must be a number conforming to the specified constraints
Meaning: The
amount field is missing.Solution: Ensure that you provide a valid amount in the amount field before sending a request to the initiate payment endpoint.No matching smart routing rule. Using default provider order.
No matching smart routing rule. Using default provider order.
Meaning: The provided
paymentMethod field or currency field does not match your configured smart routing rule or is missing.Solution: Ensure that you provide a valid paymentMethod and currency that matches your smart routing rule before sending a request to the initiate payment endpoint.MerchantOrderId must be longer than or equal to 1 characters / merchantOrderId should not be empty / merchantOrderId must be a string
MerchantOrderId must be longer than or equal to 1 characters / merchantOrderId should not be empty / merchantOrderId must be a string
Meaning: The
merchantOrderId field is missing.Solution: Ensure that you provide a merchantOrderId field before sending a request to the initiate payment endpoint.Currency must be longer than or equal to 3 characters / currency must be a string
Currency must be longer than or equal to 3 characters / currency must be a string
Meaning: The
currency field is missing.Solution: Ensure that you provide a valid currency field before sending a request to the initiate payment endpoint.Currency not supported by merchant
Currency not supported by merchant
Meaning: The currency provided in the payment request is not supported by the gateway that Archefusion routed the payment to. This typically happens when no smart routing rule matches the transaction currency and the default gateway does not support it.Solution: Configure a smart routing rule for the currency you want to accept and ensure at least one active gateway supports it. Visit the supported gateways and payment methods page to see which currencies each gateway supports.
Payment not found
Payment not found
Meaning: The provided
paymentId in the verify payment request is invalid.Solution: Provide a valid paymentId.No active payment gateways configured
No active payment gateways configured
Meaning: Your connected payment gateways are inactive.Solution: Navigate to Payment Gateways > Gateway Providers and select your connected gateway. Toggle the gateway status to active.
Korapay customer email is required
Korapay customer email is required
Meaning: The
customer.email field is missing.Solution: Ensure you provide a valid customer email address in your initiate payment payload, especially when you have the Korapay gateway configured.