Commerce sheet
Keep every language path tied to one transaction truth.
An offer can be presented differently for a defined audience, but price, consent, provider state, confirmation, fulfilment, refund, support, VAT review, and reconciliation must remain coherent across the Belgium service.
| Commerce board | Questions to decide | Cross-language review |
|---|---|---|
| Offer | Approved service or item, EUR or other currency display, amount, timing, eligibility, terms, and support. | Meaning, totals, conditions, and next step remain equivalent unless variation is documented. |
| Provider | Merchant account, country/currency support, authentication, settlement, fees, restrictions, and callbacks. | Provider-hosted and return-page language states are understood by the selected audience. |
| Transaction | Pending, accepted, declined, abandoned, delayed, duplicated, reversed, refunded, disputed, and adjusted states. | Every state has accurate customer language and the same internal record. |
| Records and VAT | Invoice or receipt content, VAT/tax interpretation, retention, refund evidence, and accounting ownership. | Qualified owners accept required records and disclosures for each affected journey. |
| Fulfilment and support | Which state begins work, who handles exceptions, how status changes, and how settlement reconciles. | Support can identify the transaction and explain the approved next action in scope. |
Provider proof
An available API is not an approved commerce route.
- Business confirms merchant and provider eligibility directly
- Qualified owner decides VAT, tax, accounting, and disclosure duties
- Language reviewers accept all customer-facing transaction states
- Engineering tests duplicate, delayed, abandoned, and refund behavior
- Support and finance owners accept recovery and reconciliation
Commission the transaction