B BNPL Integration Lab
Implementation blueprint
Connecting…

INTERNAL TECHNICAL DEMONSTRATION

One payment model.
Two BNPL providers.

A source-backed implementation lab for checkout, retail links, callbacks, payment operations, failure paths, and provider-status checks.

What this proves

The standard integration can be built from the published API documentation. This public deployment simulates the documented contracts; provider credentials and go-live approval remain external gates.

1Documented contractRequest fields, endpoints, states, and sources are mapped.
2Runnable simulationSuccess, rejection, cancel, expiry, capture, and refund are testable here.
3Provider proof pendingReal sandbox calls require provider-issued credentials and account settings.

01

Create checkout

Use mock mode now or real sandbox credentials later.

Checkout journeyChoose the customer handoff before selecting a provider

DOCUMENTATION COVERAGE

Tabby online journey controls

View evidence
Tabby
Pay in 4 interest-free payments4 payments of 62.50 SAR
Hosted checkout previewEnglish · Browser checkout · automatic merchant capture
What “Close / cancel” and “Check status” mean

Close / cancel calls Tabby’s documented Close Payment endpoint for an authorized, uncaptured online payment.

Check status is our merchant-side label for Tabby’s Retrieve Payment request; Tabby does not expose an operation named “reconcile”.

Required before displaying TabbyMinimal Checkout API payload · status created or rejected
Complete Tabby payload mapping

The generated request includes buyer, shipping address, item array, buyer history, order history, metadata, language, merchant code and all three return URLs.

02

Provider controls

Register server callbacks when using real sandboxes.

Public callback base

—

Use a public HTTPS tunnel for real provider webhooks. Localhost is sufficient for mock mode.

Internal order
→
Provider adapter
→
Hosted checkout
Webhook + status check

03

Payment ledger

↗

No sandbox payments yet

Create a checkout session to begin the demonstration.

04

Webhook audit

Persisted intake records demonstrate duplicate detection and processing outcomes.

No webhook events received.

PAYMENT OPERATION

Enter amount