Repeated action
Refresh, double-click and retry without creating duplicate charges or silent duplicate orders.
Route 04 / map the whole transaction
A payment path is a chain of responsibilities.
Do not begin with a gateway logo. Begin with the offer, buyer, merchant, currencies, provider accounts, confirmation, fulfilment, failure, refund, support and financial record that the organisation actually needs.
Transaction ledger
Seven states the build must explain.
Banque du Liban oversees Lebanon's national payment system and publishes lists of supervised institutions, including electronic payment service providers. Provider availability and terms still need direct verification for the merchant, geography, account and launch date.
- OfferWhat is sold, by which legal entity, under which terms, and when does the buyer see price, currency, tax, timing and cancellation information?
- ProviderWho owns the merchant account? Is the provider authorised and available for this specific transaction? Who completes onboarding and compliance review?
- IntentHow does the system prevent accidental duplicate orders, expired totals, tampered amounts and an order record that disagrees with the provider?
- ConfirmationWhich provider event is authoritative? What does the customer see while status is uncertain? Which message proves acceptance without overpromising fulfilment?
- FailureWhat happens after decline, timeout, abandoned redirect, lost webhook, repeated callback or a connection interruption?
- ReversalWho may cancel or refund, how is partial value handled and how do the customer, provider and internal record stay aligned?
- ReconciliationWho compares orders, provider settlements, fees, refunds and accounting records—and what queue receives a mismatch?
Release tests
Test the uncomfortable paths on purpose.
A successful sandbox payment proves very little by itself. Release evidence should include the failures the operation will have to understand and repair.
Uncertain status
Lose the browser response or delay the provider event and show a recoverable, truthful status.
Reversal
Exercise cancellation and refund permissions, confirmation and record alignment.
Mismatch
Create a reconciliation difference and verify that it reaches a named human queue with enough evidence.
Official checkpoints
Verify the provider and payment environment.
These central-bank pages are direct starting points. They do not approve a provider for your project or replace legal, tax, accounting, sanctions or financial-compliance advice.
BDL payment system
Banque du Liban describes the components and oversight of Lebanon's national payment system.
Review the official overviewSupervised institutions
BDL publishes current institution categories, including electronic payment service providers.
Check the official listsEngagement boundary
The client owns merchant eligibility, commercial policy, tax and regulated decisions. Faith Forge Labs implements approved technical flows.
Review ownership boundaries