Map / Commerce & payments

Map the money route end to end.

A checkout or invoice is only one waypoint. Pricing, evidence, settlement, refunds, reconciliation, support, and accounting records must still agree.

Commerce route

Decisions to make before integration.

Faith Forge Labs can implement confirmed business rules and provider flows. The client and qualified advisers remain responsible for tax treatment, disclosures, accounting policy, and regulatory conclusions.

Offer & currency

Define what is sold, whether prices display in NZD, when conversion happens, what a quote includes, validity period, renewal or usage rules, and which terms govern.

Customer evidence

Decide what customer status or location evidence is needed, how it is collected, when it is challenged, and who can correct it. Avoid collecting more identity data than the purpose requires.

Tax decision

Record the tax position supplied by the organisation or adviser, including GST registration assumptions, business-versus-consumer handling, evidence requirements, and invoice fields.

Payment state

Model authorised, captured, failed, disputed, refunded, partially refunded, and cancelled states. A provider success screen is not a substitute for a verified server-side state.

Ledger & receipts

Name the financial source of truth, receipt delivery, reference identifiers, settlement records, fee handling, exchange-rate evidence, and the correction path.

Reconciliation & support

Define how provider events match orders and bank deposits, who reviews exceptions, what evidence support can see, and how records are retained.

Remote services need a verified GST position.

Inland Revenue’s current guidance says a non-resident business supplying remote services from outside New Zealand to New Zealand resident customers may need to register for, collect, and return GST. The examples include software, software maintenance, website design, web publishing, and consultancy services. The guidance also distinguishes some supplies to GST-registered New Zealand businesses for business use.

That makes customer type, New Zealand residency evidence, expected sales, contract structure, and professional advice project inputs—not assumptions to bury in code. Requirements can change, so the official page should be checked again before launch.

Read Inland Revenue: supplying remote services into New Zealand.

No tax advice is being offered here. This page identifies implementation questions. Confirm the applicable GST and accounting treatment with Inland Revenue guidance and an appropriately qualified adviser.

A reliable payment release has a rollback route.

  • Use provider test modes and representative scenarios.
  • Verify webhook signatures and make event processing repeat-safe.
  • Prevent duplicate fulfilment when events arrive more than once or out of order.
  • Show users a recoverable failure message without exposing internal details.
  • Reconcile a controlled live transaction before scaling traffic.
  • Document how to disable the new route without corrupting order records.

One money route

Start with the transaction that matters.

Map the offer, states, evidence, owner, and reconciliation path.

Start the commerce map