Register the reader in the Stripe Dashboard or via the Terminal API by providing the reader's registration code displayed on the device screen; the response returns a Reader object with an ID.
On your server, create a ConnectionToken by calling the Terminal connection tokens endpoint; pass this token to your point-of-sale application to authenticate the Stripe Terminal SDK.
In your POS application, initialize the Stripe Terminal SDK with the connection token provider and connect to the reader using its ID; for the WisePOS E this is done over your local network.
Create a PaymentIntent server-side for the transaction amount and pass the PaymentIntent client secret to the Terminal SDK's collectPaymentMethod method.
After card collection, call processPayment on the SDK, which communicates with the reader for card dip/tap/swipe and returns the confirmed PaymentIntent.
Capture the PaymentIntent server-side if it was created with capture_method set to 'manual', or let it auto-capture; then print or email a receipt using the payment details.
Known gotchas
The WisePOS E connects over WiFi and must be on the same network as your POS device for local connection mode; internet connection mode uses a different connection method and has higher latency.
Terminal PaymentIntents require the payment_method_types to include only card-present payment methods; attempting to confirm a Terminal PaymentIntent with a card-not-present method will fail.
Reader software updates are required periodically; if a reader is offline for an extended period, it may require an update before processing the first transaction, which can delay service.
Give your agent this knowledge — and 15,500+ more routes
One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp
Need this verified for your stack — or a route we don't have yet?