- 0:00–0:06
Bring one test order • Use the same example with each provider. • Order A • Order reference • Payment brief • Requirements open
The GPT Image Order reference document sits within the illustrative Order A record. A directional trace enters Payment brief. Requirements open is highlighted; eligibility, methods and supported route still need confirmation.
- 0:06–0:12
Confirm the supported route • Record the connector and account approval separately. • Connector review • Merchant approval: pending
Connector review and Merchant approval: pending are highlighted separately. Technical installation does not approve a merchant account.
- 0:12–0:18
Test a closed browser • Match reference, amount and currency. • Browser closed • Provider • Verify • Order A · Review • Event
Browser closed stays disconnected. An Event moves from Provider to Verify and then Order A · Review. Reference, amount and currency must be matched. No paid state or successful test is shown.
- 0:18–0:24
Test repeated notifications • The expected fulfilment instruction is issued once. • Order A • First event • Repeated event • Expected: fulfil once • Test evidence required
First event and Repeated event move into the same Order A record. Expected: fulfil once is highlighted, followed by Test evidence required. This states a test expectation; it does not report an actual successful duplicate-event test.
- 0:24–0:30
Match the finance records • Give finance the references it needs. • Order A • Order reference • Payment • Deductions • Settlement
The same Order A reference document connects in turn to Payment, Deductions and Settlement. These are non-directional reference links for finance to compare, not transfers or a completed reconciliation.
A silent illustrative guide to payment verification, repeated notifications and matching finance records for one test order.
Read the article: Payment Gateways Saudi Arabia: A Store Buyer’s Guide