Developers Guides Paths SoftPOS only

SoftPOS only

SoftPOSTap to PayiOSAndroidNo Hardware

Tap to Pay on iPhone and Android with no hardware: your app beside the CheckoutX app on the same device, then orders, refunds and receipts from your own app.

13 guides in reading order. Read them on the site, or take the whole path as one markdown file for your coding agent.

Add this to your codebase

Paste it into Claude Code, Codex, Cursor or any coding agent. It points the agent at this guide in machine-readable form, so it writes against the real API instead of a guess. Wire up the MCP server once and it can read the rest of the platform too.

01 Get access 1 guide
02 Payment application 2 guides

Go with CheckoutX and the inter-app integration. CheckoutX is the certified payment application, so the PCI and Apple submissions and the compliance that follows sit with Surfboard, not with you, and your app is a normal app that hands off each payment with an app switch. The SDKs put Tap to Pay inside your own app instead, and that moves the submissions to PCI and Apple, the security reviews, and the ongoing compliance work onto your product.

Also available, not on the recommended route

  • Tap to Pay on iPhone SDK: The iOS SDK, if Tap to Pay has to live inside your own iPhone app and you are prepared to carry the Apple and PCI submissions yourself.
  • Android SoftPOS SDK: The Android SDK, on the same terms: your app becomes the payment application, and its compliance becomes yours.
03 Payment flow 5 guides
04 Merchants and operations 4 guides
05 Branding 1 guide