The provider never answers
Keep the request idempotent, show an honest pending state, avoid duplicate charges, and give support enough information to resolve the transaction.
Money trail
A payment journey needs a way home from every dead end.
NOK presentation, the contract currency, provider settlement, tax handling, receipts, fulfilment, and accounting can be separate layers. The route must identify the owner of each layer and show what happens when their records disagree.
The payer or service is ineligible
Provider, bank, customer, service, location, identity, and platform rules can change. Confirm eligibility through current client-owned relationships before relying on a route.
The system says paid; settlement does not
Define reconciliation, exception ownership, evidence, refund authority, and when fulfilment may proceed. A dashboard number is not the final ledger.
The commercial assumption expires
Assign owners for provider terms, tax treatment, invoices, currency display, and customer notices so the product can change without guesswork.
Official starting points
Ask the specific question.
The Norges Bank payment-system material provides infrastructure context. The Norwegian Tax Administration page on remotely deliverable services can help frame a tax question. The client and qualified advisers determine what applies to the real parties and service.
Commerce acceptance kit
Require an approved price and currency display, successful and failed sandbox journeys, duplicate protection, a pending-state policy, receipt and refund wording, settlement reconciliation, protected credentials, and a named commercial owner.
Do not infer
This field guide does not establish provider acceptance, a VAT result, accounting treatment, identity assurance, availability, or a right to serve a particular customer.
Bring one transaction and its three records.
Show the user-facing state, the provider record, and the organisation's system of record. The differences reveal the engineering work.