Going live

11.1 What you need

• UAT signed off by InnBucks, and the video accepted (10.4)
• All account-opening documentation completed with InnBucks
• Your business administrator nominated, so you can use the business portal (3.4)

11.2 Steps

1. InnBucks sets up your production account and sends production API credentials and the production base URL.
2. InnBucks explains how to pre-fund your merchant account. If you do deposits, bank change or utility payments, expect them to draw on that balance.
3. InnBucks trains you on the reversal process, help-desk queries and contacts, and merchant statements (including online access through the business portal).
4. Switch your configuration: production base URL, API key, username, password and INNBUCKS_ENV=production (which switches the deep link to com.innbucks.customer://).
5. Make one small real payment end to end and check that it appears on your statement.

11.3 Go-live checklist

• Production credentials are in the secret manager, not in code or in the repository
• Base URL, API key, username and password all come from the same environment
• Deep links use com.innbucks.customer://purchase?paymentToken=
• The token is cached and refreshed at 14 minutes; 401 triggers one re-login
• Amounts are sent as integer cents everywhere (check a US$4.50 order sends 450)
• narration carries your unique reference, for statement reconciliation
• Code inquiries run in a background job, one per code every 30 seconds
• Orders are fulfilled only on Claimed or Paid, and only once
• Money-moving requests are never re-sent after a timeout
• Every call logs responseCode, message, HTTP status and X-Trace-Id, and no secrets
• The payment screen follows the brand guidelines (5.6)
• Someone reconciles the InnBucks statement against your orders daily

---

This page is generated from section 11 of the README in README.md. Spotted something wrong? Open an issue.