Skip to main content

Go-live checklist

Before going live, be able to demonstrate each of the following. This is what a Boundless integration review will walk through with you. Read it early — it tells you what "done" means.

Payment​

  • Create a payment; the terminal displays the amount; the response is AWAITING_TERMINAL
  • A successful tap resolves the till screen via sync-status polling
  • A declined card resolves to REFUSED and the till offers another tender
  • The customer walks away; the payment reaches a final state and the till screen resolves
  • The payment id is persisted against the bill before the cashier sees anything
  • Polling stops once the payment reaches a final state

Reversal​

  • Cancel a waiting payment from the point of sale; verify the amount clears from the device
  • Cancel the payment at the terminal; the till discovers CANCELLED on its next sync-status and closes the bill cleanly without treating it as an error
  • A cancel raced by a completing payment; the till reads the returned status and does not treat it as cancelled
  • Void a captured payment inside the window; the payment reads CANCELLED
  • A void returns 200 with the payment still CAPTURED; the till does not report success, and re-reads or retries
  • Retry a void that already succeeded; the till reads the 409 plus the CANCELLED status and reports success, not failure
  • Attempt a void outside the window; the till surfaces the refusal to the cashier as a back-office matter, not as a system error

Resilience​

  • A create times out with no response; a retry with the same reference returns the same payment — no duplicate payment
  • A second payment created on a busy terminal returns REFUSED; the till handles it as a busy device, not a card decline
  • 429 is handled with Retry-After backoff
  • The till goes offline mid-sale and recovers; the payment's final state is picked up on restart

Operations​

  • A "check payment" button calls sync-status
  • A disputed bill can be traced end to end from its status history
  • The API key is held server-side only; no key on a terminal or in a client binary
  • Key rotation is exercised without downtime

When every box checks, contact Boundless to schedule the integration review.