Skip to main content
A payment is authenticated either with an OTP code or with a redirection link. The following providers support authentication through a redirection link:
  • Wave
  • Ecobank CI
  • Orange CI and Orange SN
For Orange, the redirection workflow must be requested in the payment attempt: set mobileMoney.workflow to redirection and provide both mobileMoney.onCancelRedirectionUrl and mobileMoney.onFinishRedirectionUrl. If either URL is missing, the request is rejected with a 400 error (invalid_url). The redirection URL is in the nextAction object, for example:
Everything needed to perform the redirection is in the nextAction.data field.

Important

In this example, the customer is redirected with a GET request to https://pay.wave.com/c/wrongUrlForDemo.
HUB2 updates the status of the Payment object once the provider has processed the payment.

Authenticate the payment with an OTP

When nextAction is of type otp, authenticate the payment with the dedicated endpoint and the confirmation code (confirmationCode) provided by the end customer. Authenticate payment Note: this request can also be sent directly from the client side, using the JWT token.

Orange CI and OTP

When a payment is attempted with Orange CI using an OTP, Orange applies a 10-minute timeout.
The payment expires after that timeout, which can degrade the customer experience. To avoid this, ask the customer for the OTP first, before attempting the payment. Once the customer provides the OTP, attempt the payment and include the OTP directly in the request:
HUB2 sends all the information to Orange, which processes the payment immediately, without a separate authentication step.