capabilities.work

Charge with OTP Notification

A 4-step recipe with Cellulant. We can help you get access.

Recipe · 4 steps

Charge with OTP Notification

Initiate a custom checkout, SMS an OTP, then charge the customer.

  1. Exchange the client credentials for a bearer access token used to authorize the checkout and charge calls.
  2. Initiate a host-to-host custom checkout and capture the checkout_request_id.
  3. Deliver a one-time passcode to the customer by SMS through Tingg Engage.
  4. Post the charge request against the initiated checkout to debit the customer once the OTP has been delivered.
What you'll need to have ready
  • clientId: OAuth client id issued in the Tingg dashboard.
  • clientSecret: OAuth client secret issued in the Tingg dashboard.
  • apiKey: Merchant apikey header value issued in the Tingg dashboard.
  • merchantTransactionId: Unique merchant transaction id for this checkout.
  • serviceCode: Tingg service code identifying the merchant product line.
  • countryCode: ISO 3166-1 alpha-2 country code.
  • currencyCode: ISO 4217 currency code.
  • requestAmount: Amount to charge the customer.
  • callbackUrl: IPN callback URL Tingg posts the payment result to.
  • msisdn: Customer phone in E.164 format.
  • payerMode: Custom checkout payer mode (MOBILE, BANK, or CARD).
  • paymentOptionCode: Payment option code identifying the rail to charge.
For your developer

Arazzo workflow cellulant:charge-with-otp-notification, 4 operations: requestAccessToken → initiateCustomCheckout → sendEngagement → initiateChargeRequest. Specs on APIs.io.