A payment can be authenticated either using an OTP code or a redirection link.

The following providers allows redirection link authentication method:

  • Wave
  • Ecobank CI
  • Orange CI/SN

To retrieve the redirection URLs, please check in the nextAction object, that would look like that:

{
    "nextAction": {
        "type": "redirection",
        "message": "mm_wave_live.redirection",
        "data": {
            "url": "https://pay.wave.com/c/wrongUrlForDemo",
            "method": "get",
            "headers": {},
            "data": {}
        }
    }
}

All the necessary information to perform the redirection properly is located in the nextAction.data field.

Important

In this example, that would be a request to GET https://pay.wave.com/c/wrongUrlForDemo.

HUB2 will return the Payment object and will update the status after contacting the provider.

​
Authenticate the payment using OTP

For nextAction of type otp, payment authentication will be required using the dedicated endpoint and the confirmation code confirmationCode provided by the end customer.

Authenticate payment

Note: This request can also be sent directly from client side using the JWT token.

​
Orange CI & OTP

When attempting a payment using Orange CI and method OTP, Orange will have a 10 minutes timeout.

The payment will be expired after that timeout, which can lead to poor user experience for the clients.

Good practice here to avoid that case is to ask the OTP to the client first, before attempting the payment.

Once the client provides the OTP, call our endpoint to attempt a payment, directly providing the OTP.

HUB2 will reach Orange with all the information and they will process the payment immediately.

IntegrationList payments