Skip to content

Who it's forOnline retail

Sell online, collect every order.

Your customers pay by mobile money or card, on a page in your colours or inside your own pages. If a mobile money connection fails, the payment goes through another.

Aïcha K.Douala, Cameroon
  1. Payment of 5,000 XAFMTN MoMo · order #4172just now

The money's journey

From the cart to the confirmed order.

Every step runs on a Wajub product, from the payment page to the confirmation on your server.

  1. Payment of XAF 5,000MTN MoMo · order #4172

    The customer pays

    On the Wajub payment page in your colours, or inside your pages with Components: mobile money and cards in one place.

    Checkout

  2. Automatic failoverCampay unreachable, pawaPay takes over

    A connection fails, the payment carries on

    With mobile money, another of your connections picks up the request. The customer has nothing to redo.

    Orchestration

  3. Order confirmedShield · risk 12/100

    Shield scores the payment

    A doubtful payment is collected, then joins your review queue. A payment that is too risky is declined.

    Shield

  4. Order #4172 paidpayment.succeeded · webhook delivered

    Your server is notified

    The webhook arrives even if the customer closed the page. You ship on that confirmation.

    Payments

What Wajub puts in place

A payment page ready to go, or your own.

Checkout and Components share the same payment methods and the same failover. Only where the payment happens changes.

  • Checkout

    Checkout, the hosted page

    Your customer goes to a Wajub page in your colours, then comes back to you.

    • Your logo, colours and font
    • Mobile money and cards on a single page
    • Your own domain with Scale
  • Components

    Components, inside your pages

    The payment shows inside your site: your customer never leaves it.

    • The full checkout in one component, or separate fields
    • Confirmation codes and 3-D Secure handled
    • The card number goes through neither your server nor Wajub
  • Shield

    Shield, on every payment

    Every live payment is scored, on every plan.

    • Your own thresholds
    • A review queue for doubtful payments
    • Rules and lists with Shield Advanced

Good to know

Before you start, what you should know.

  • A card is never replayed

    Failover applies to mobile money. A card payment stays with its provider.

  • A closed page does not stop the payment

    The payment carries on with the operator, and the webhook still reaches your server.

  • Ship on the webhook

    The browser coming back is not enough to confirm an order: wait for Wajub's confirmation.

The recommended plan

Growth

For a payment page in your colours and your own routing rules.

$17

/ month

Billed monthly, no commitment

Choose Growth
  • Checkout appearance
  • Routing rules
  • Up to 6 connections

Next : Scale. To serve the payment from your own domain, with Shield Advanced included.

See all plans

Frequently asked questions

Another question? Talk to sales

What happens if my customer closes the page before the end?
The payment carries on with the operator. If it succeeds, the webhook still reaches your server: ship on that confirmation, never on the browser coming back alone.
Checkout or Components: which one should I pick?
Checkout if you want a ready page, with nothing to build. Components if the payment must stay inside your pages. The payment methods and failover are the same.
Could Shield block real sales?
A doubtful payment is not blocked: it is collected and joins your review queue, where you decide. Only a very risky payment is declined.
Can I put the payment page in my colours?
Yes, from Growth: logo, colours, font and corner radius, with a live preview in the Dashboard. The setting applies to the whole account.

Test your case in sandbox.

Create a free account, run your first payments with test numbers, then go live.