Integration prompts
Copy-paste agent prompts for Bolt checkout, embeddable payments, webhooks, and gaming payment links.
Copy a prompt into Cursor, Claude Code, or your agent harness. Each prompt links to canonical docs and OpenAPI specs.
Accept payments (managed checkout)
You are integrating Managed Checkout into an existing web app with Bolt Payments sandbox.
- Read https://help.boltapp.com/products/checkout
- Follow the single flow in the quickstart. Use platform alternatives only when the user selects one.
- Use sandbox API base
https://api-sandbox.boltapp.comfor all test calls - Use endpoint-specific authentication from the spec; keep API keys on the server.
- Verify order creation against https://assets.boltapp.com/external-api-references/bolt.yml: POST /v1/merchant/orders
- Verify the payment and matching app order, then run https://help.boltapp.com/products/checkout-test-plan. Report unrun cases as Not run.
Do not invent fields. Mark anything not in the spec as BLOCKED.
Embeddable checkout
You are adding Bolt payment fields to a custom checkout UI.
- Read https://help.boltapp.com/products/embeddable-checkout and https://help.boltapp.com/api-reference/guides/embeddable-checkout
- Default to Embeddable API v1: verify against https://assets.boltapp.com/external-api-references/embedded.yml
- Load connect.js from connect-sandbox.boltapp.com in sandbox
- Use publishable key client-side; API key server-side only
- Verify the payment and matching app order, then run https://help.boltapp.com/products/embedded-api-test-plan.
Do not promote v3 unless explicitly requested.
Checkout Everywhere
Follow https://help.boltapp.com/products/checkout-everywhere using its BigCommerce sandbox flow. Verify the same product through the link and QR code, then reconcile the Bolt payment and store order. Run https://help.boltapp.com/products/checkout-everywhere-test-plan. Other platforms use their own setup guides; do not mix instructions across stores.
Marketplace Connect
Follow https://help.boltapp.com/products/connect for one seller and one sandbox payment. Preserve server-owned seller identity and verify the matching order. Run https://help.boltapp.com/products/connect-test-plan. Payment completion does not prove payout settlement. Flag unavailable account enablement instead of substituting another flow.
Verify webhooks
You are implementing Bolt webhook signature verification.
- Read https://help.boltapp.com/api-reference/guides/verify-webhooks/
- Use signing secret from Merchant Dashboard → Administration → API
- Verify HMAC on inbound requests before processing payload
- Reject invalid signatures. For valid events, use the documented acknowledgement and durable processing flow.
- Expected result: forged requests rejected; valid webhooks update order state
For cart, shipping, and tax callbacks Bolt calls on your server, see Merchant Callback.
Gaming payment links
You are integrating in-game checkout links.
- Read https://help.boltapp.com/gaming/guide/quickstart/
- Create sandbox merchant account at merchant-sandbox.boltapp.com
- Verify the payment-link request against https://help.boltapp.com/gaming/guide/bolt-api/create-payment-link/. Gaming endpoints are not in the published general OpenAPI specs.
- Handle webhooks per https://help.boltapp.com/gaming/guide/bolt-webhooks/validate-authenticity/
- Verify the payment on the server and grant the correct reward once. Identify any missing app-owned persistence or retry logic before claiming completion.
Use Unity C# or JavaScript SDK labels consistently in CodeGroups.