Jump to Content
AlacrityGuidesAPI ReferenceDiscussions
HomeGuidesAPI ReferenceChangelogDiscussions
v2.2

GuidesAPI ReferenceDiscussionsLog InAlacrity
Log In
v2.2

Documentation

  • Introduction
    • Integrating a new service
    • Mobile Operators
    • User Journey Requirements
    • API Standards
    • Partner Responsibilities
  • The Alacrity Portal - getting started
  • The Sandbox Environment
  • Supported Business Flows
    • One Off Charge
    • Checkout (including Two Click)
    • Pin Flow (OTP)
    • Pin Flow with Header Enrichment
    • MO SMS
    • Refund
    • Two Click
    • MO SMS Requiring Reply
  • Exempting MSISDNs
  • Subscription API Usage
    • Subscription Renewal
    • Subscription Status
  • Send SMS
  • Delete Subscription (Unsubscribe)
  • Eligibility Check
  • HTTP Notifications
  • Transaction Status
  • Errors
  • Check Transaction

Checkout

  • Checkout
  • Hosted Button Integration
  • Empello FraudStop - Traffic Insight

Operator Variations

  • Axiata
  • Etisalat UAE
  • Ooredoo Kuwait
  • STC Kuwait
  • Telenor (all)
  • UK
  • U Mobile Malaysia
  • Unitel Mongolia
  • Zain Iraq
  • Zain Kuwait
  • Zain KSA SDP
  • Zain KW SDP
  • 9mobile Nigeria

Fraud Prevention

  • Fraud Prevention
Powered by 

Etisalat UAE

Suggest Edits

Regulations within Etisalat and the UAE require landing pages to be hosted by the DCB partner and not downstream merchants. Merchants must therefore redirect from promotions directly to checkout.

Typical Flow

  1. User interacts with promotional material
  2. Merchant directs immediately to checkout from promotion
  3. Merchant makes create call with TOKEN returned from checkout

Updated 8 months ago


What’s Next
  • Checkout
  • Subscription API Usage
  • Table of Contents
    • Typical Flow