Skip to content

Shield

Every payment scored from 0 to 100, before it reaches the provider.

Shield scores the risk of every live payment from 0 to 100, before Wajub calls the provider. From 50, the payment goes through and joins your review queue. From 80, it is declined and nothing is charged.

Activate ShieldRead the documentation

Free to activate in one click from the Dashboard, on every plan.

The decision

One score, three outcomes, before the provider.

Each payment gets a score from 0 to 100 based on the signals found. The platform thresholds apply until you activate Shield; once it is active, you set them yourself.

  • 0 to 49

    The payment goes through

    It goes to the provider chosen by routing, as if Shield were not there.

  • 50 to 79

    Collected, then reviewed

    The payment is never held: it is collected and joins your review queue. Check it before you deliver.

  • 80 to 100

    Declined before the provider

    No provider is called and nothing is charged. The API returns 403 with a BLK reference; on the Wajub payment page, your customer sees "Payment failed".

An example decision

The score takes every signal found on the payment into account. The reasons for each flagged payment show in your review queue.

Sanctions lists

A customer on the OFAC or UN sanctions lists is declined on every plan, even if a rule allows the payment.

Your thresholds

Stricter than Wajub, never more lenient.

Once Shield is active, you set the block threshold between 40 and 80, and the review threshold between 10 and just below the block threshold. On every plan.

Without your settings, the platform protection applies: declined at 80, review at 50.

The review queue

The payments to check, with their reasons.

Each flagged payment stays in the queue for 90 days, with its reasons in plain words. The payment's page keeps its score, the decision, the IP address, the country of origin and the device.

  • ApproveOn every plan

  • Always allow this customerWith Shield Advanced

  • Block this customer, with or without a refundWith Shield Advanced

Shield Advanced

Your own rules, written as sentences.

Included in Scale and Enterprise. On Pay as you go and Growth: XAF 14,900 per month.

Rules

Up to 10 conditions, all true at once, then one action: block, send to review, request 3D Secure or allow. Rules run from top to bottom and the first one that matches decides. In test mode, a rule counts its matches on real payments without deciding anything.

Amount, currency, payment method, email, phone, IP country, customer's first payment, presence on the blocklist.

A blocklist

Block an email, a phone number, an IP address, a country or a card BIN.

Blocking a BIN depends on the provider that processes the card.

Auto 3D Secure

Card payments that reach the review threshold go through 3D Secure, with Stripe and Adyen. Off by default.

Signals

What Shield looks at, depending on your plan.

Shield checks card and mobile money payments alike, from what Wajub knows about the customer and their device.

On every plan

  • IP, number and card country
  • Device, browser and connection
  • Customer's number and email
  • Attempt patterns
  • Amount unusual for your business
  • Customer's dispute history
  • OFAC and UN sanctions lists

With Shield Advanced

  • Finer checks on the device, the card and the email
  • Card testing and repeated declines
  • Signs of a SIM swap
  • Lost disputes across all of Wajub
  • Customers you flag as risky

Developers

On your own checkout, send the browser signals.

Wajub payment pages send the data._client block on their own. On your own checkout, add it to the payment request so Shield can check your customer's browser.

  • A decline is a 403

    With a BLK reference, without saying which signal counted. The payment is not changed.

  • Your settings through the API

    Read and change your thresholds, statistics and blocklist with your live keys.

    /shield/settings/shield/stats/shield/blocklist

  • The score stays in the Dashboard

    The API returns neither the score nor the reasons, and no webhook carries them: read them in the Dashboard.

  • Live mode only

    Shield decides nothing in sandbox: your test payments are never blocked.

Charge with the browser signalsPOST /payments/{id}

{  "channel": "card",  "data": {    "payment_method_id": "pm_1PqR8xLkdIwHu7ix0aB3cD4e",    "_client": {      "timezone": "Africa/Douala",      "language": "fr-CM",      "screen": "1512x982",      "color_depth": 24,      "fingerprint": "9f2c41ab7e05d3c8"    }  }}

Payment declined403 Forbidden

{  "code": 403,  "status": "Forbidden",  "message": "Payment blocked: transaction risk score too high. Please contact support and reference BLK-K3M9XQ2P."}

Frequently asked questions

Another question? Talk to sales

Is Shield included in my plan?
Yes. Every live payment is analysed on every plan, with your own thresholds and a review queue. Shield Advanced (rules, lists, automatic 3D Secure) is included in Scale and Enterprise, and available as an add-on on other plans.
Is a flagged payment held?
No. A flagged payment is collected normally and joins your review queue. If you want to hold a delivery while you check, handle it in your own system.
What is the score based on?
On the signals found during the payment: location, device and browser, number and email, attempt patterns, amount, customer history. No black box: the signals found are recorded on each payment, and the review queue shows the reasons for every flagged payment.
Can I be less strict than Wajub?
You can be stricter, never laxer: the platform blocks at 80 and flags at 50 by default, and a higher block threshold is brought back down to it.
Can I test Shield in sandbox?
Sandbox payments are not scored. To measure a rule's effect, use Shield Advanced test mode: the rule is evaluated on your real payments and counts its matches, without deciding anything.

Activate Shield on your account

Free on every plan, in one click from the Dashboard. Shield Advanced when you want your own rules and your blocklist.

Activate ShieldRead the documentation