All-In-One App Simulator

End user applies in the BNPL app, KYC is shared with the issuer, screening runs, the card is issued and funded from the stored value account. Five app sections: Home (book hotels, flights, taxis and holidays), Wallet, Card, Pay later and Trade. Tap the card at a POS with debit or Pay later, shop partner stores in instalments, trade crypto, and fund the card from the USD wallet. Add the card to Apple Pay, Google Pay or Samsung Pay through in-app provisioning. Every hop, rule and ledger line is shown on the right.

VYBE app · sample BNPL program manager (B2B client)

Issuer console

BNPL (VYBE) Issuer SDK in app Issuer platform Mastercard MDES Wallets & third parties Ops & compliance

Parties in the programme

Party	Role	Phase 1 touchpoint	PCI DSS scope
Mastercard	Scheme	BIN range, prepaid consumer product, card profile	—
Mastercard MDES	Token service provider	Eligibility, tokenisation, Tokenization Authorization Request to issuer, activation codes, token lifecycle	Scheme
Wallet providers	Apple, Google, Samsung	Add-card sheet, wallet risk score, token storage on device	—
Issuer processor	Principal member, BIN sponsor, processor	KYC/AML decision, card management, HSM, PAN vault, rules, ledger	In scope (Level 1)
BNPL company	B2B client, programme manager	App, onboarding, KYC capture, SVA (when BNPL holds funds)	Out of scope via SDK
End user	B2B2C cardholder	Applies, picks design and form factor, loads and unloads	—
Issuer SDK	Issuer code inside the BNPL app	Secure card views, issuer API calls with short-lived session	Issuer's scope
Screening vendors	e-Spear and similar	Sanctions, PEP, adverse media	—
Card bureau	Personalisation and delivery	Embossing, chip perso, courier tracking	In scope (CPP)
Travel suppliers	Hotels, airlines, ride and holiday partners	Search, hold, confirm and cancel via API; paid by VYBE net of commission	—
Credit bureau	BENEFIT CRB, AECB or SIMAH	Credit report and score for the VYBE Pay later limit	—
Merchants and acquirers	Partner stores, POS acquirers	Pay later checkouts settled by VYBE (MDR); card taps routed through Mastercard	Acquirer scope
Crypto liquidity provider	VYBE's execution venue	Fills crypto-to-USD sells for the VYBE USD wallet. Issuer has no contract or visibility	—
Safeguarding bank	Holds customer funds	Backs SVA and card balances in issuer-held model	—

Build phases

Issuance and funding

KYC share, screening, card creation, SVA top-up, load and unload, ledger. This page.

SDK inside the app simulator

Session lifecycle, secure views, PIN pad, error contract, webhooks, SDK versioning.

Tokenisation and wallets

In-app push provisioning to Apple Pay, Google Pay and Samsung Pay with green, yellow and red decisions and token lifecycle: live now. Next: in-app NFC (HCE) payments.

Authorisation and payment choice

Live now: contactless tap with ISO 8583 0100/0110, debit vs Pay later choice and the All-in-One amount rule with JIT funding. Next: 3DS and e-commerce.

Clearing, settlement, instalments

IPM clearing, settlement to Mastercard, BNPL plan creation, repayments from linked bank, disputes.

Wearables and IoT

EMV chip rings and bands, form-factor lifecycle, replacement and re-binding.

Design decisions baked into Phase 1

KYC reliance does not move accountability. The BNPL captures KYC, but the issuer still owns the AML decision under CBB rules. The simulator re-screens every applicant and keeps the reliance reference. You need a written reliance agreement with each BNPL client.

Numberless cards, details only in the app. Physical and virtual cards carry no printed PAN, CVV or expiry. The app shows them after a biometric step-up, for 30 seconds, through the issuer SDK or an issuer-hosted secure view. The BNPL backend only ever holds a single-use view token, so it stays out of PCI DSS scope on both integration paths.

When the BNPL holds funds, the issuer asks before it loads. Loads trigger a synchronous funding approval call to the BNPL, then draw on the programme prefund. Without that call, SDK loads could overspend the BNPL's SVA.

Green, yellow or red is the issuer's answer to MDES. The wallet sends its own risk recommendation inside the Tokenization Authorization Request, but the issuer decides. A frozen or inactive card is always red, whatever the dropdown says. Yellow creates an inactive token that only goes live after ID&V: OTP by SMS or email (3 attempts), app-to-app confirmation in the VYBE app, or a call to customer service.

Push provisioning keeps the BNPL out of PCI scope. The issuer HSM encrypts card data to the wallet's key (Apple leaf certificate, or the MDES key for Google and Samsung). The VYBE app only passes ciphertext. Freezing the card suspends every device token through MDES token lifecycle calls.

One transaction log feeds every report. Each money movement (top-up, card load and unload, POS and e-commerce authorisations, ride holds and captures, refunds and reversals, Pay later purchases and instalments, crypto trades and vendor payouts) writes a single record with status, method, channel and the revenue it earned per stream. The customer's Activity, the programme Dashboard and the Reports export all read from that log, so the numbers always agree.

VYBE is merchant of record for travel. It collects the full price on its own merchant account (card through its PSP under MCC 4722 or 4121, wallets on the issuer or VYBE ledger, Pay later on its own book) and pays each supplier net of commission. Payment only happens after the supplier holds the price, and a failed supplier confirmation reverses the payment automatically, so the customer is never charged for a booking that doesn't exist.

Flights are priced per offer, not per route. NDC and GDS suppliers return offers for the whole journey (both directions on a round trip), so the return list only shows offers from the supplier of the chosen outbound and the booking lands on one PNR. Child fares are 75% and lap infants 10% of the adult fare, with taxes added per traveller and per leg.

Rides use hold and capture. Taxi bookings hold the estimate plus 20% (a card pre-authorisation, or a wallet hold), capture the final fare with a 0120 completion when the trip ends, and release the rest. Cancelling before pickup releases the whole hold with a 0400.

Pay later at the till is JIT funding, not a second card product. When the cardholder picks Pay later (or the All-in-One rule picks it above the threshold), the issuer calls VYBE during the 0100. VYBE's credit engine approves, the issuer moves the amount from VYBE's funding account onto the card, then authorises against the card balance. The prepaid BIN stays prepaid; VYBE carries the credit risk and collects instalments by direct debit from the linked bank.

Overdue means paused, not penalised. A returned direct debit marks the instalment overdue and drops Pay later availability to zero until it's paid. That keeps the Gen Z proposition simple (no late fees) while still capping exposure.

Crypto stays outside the issuer perimeter. Crypto-to-USD conversion and the VYBE USD wallet sit under VYBE's own crypto licence; the issuer never holds or sees them. The issuer only receives a card-currency credit funded from VYBE's FX funding account, tagged funds_origin: CRYPTO_CONVERSION with the FX reference and the original USD amount, so transaction monitoring can treat crypto-origin funds differently.

The second leg converts at the GCC peg, not the market. BHD, AED and SAR are pegged to USD, so the USD-to-card-currency rate is fixed (0.376, 3.6725, 3.75) plus VYBE's margin. Price risk sits only in the crypto leg, which is why that quote locks for 15 seconds.

Rejected applicants get a generic message. Neither the end user nor the BNPL webhook receives the screening reason, to avoid tipping off.

Amounts are stored in minor units with an exponent. BHD, KWD and OMR carry 3 decimals; AED, SAR and QAR carry 2. ISO 4217 numeric codes travel with every amount.

Decide the BNPL credit model before Phase 4. Paying later at the POS on a prepaid BIN only works if the BNPL funds the card at authorisation time (JIT funding). A true credit or deferred-debit option needs a different Mastercard product setup.