mada and invoice / gate 04
National infrastructure does not create automatic merchant or API access
- Currency
- SAR
- mada access
- Through eligible client/provider
- E-invoice applicability
- Client / qualified tax owner
Define seller, invoice, and tax ownership
Identify the legal seller or service provider, customer type, products or services, price, VAT and tax owner, invoice model, currency, delivery or performance, cancellation, refunds, disputes, settlement account, and accounting record. Faith Forge Labs does not write or approve tax policy.
- Seller and customer context
- SAR display and rounding
- Invoice and VAT decision owner
- Refund and dispute process
Confirm the exact provider relationship
The client secures the merchant or invoicing relationship and current technical access. Record provider, eligibility, API and specification version, sandbox, certificates or keys, authentication, callback validation, limits, fees, support, data path, and production approval. Never store credentials in public source or logs.
- Client-owned account
- Current SAMA/ZATCA/provider material
- Signed and duplicate-safe events
- Provider outage route
Test business and technical states
Cover pending, completed, declined, duplicated, delayed, reversed, refunded, disputed, unmatched, offline, and provider-unavailable states. Reconcile the application, provider, invoice, settlement, and accounting records. Qualified owners approve production enablement after the evidence.
- Idempotent payment handling
- Invoice status reconciliation
- Accessible customer errors
- Audit, rollback, and disable path
Bring merchant, provider, invoice, and finance owners together
Share the approved relationship, current specification, invoice and tax owner, payment journey, settlement and refund process, test environment, and acceptance evidence.
Prepare the project brief