.env at startup. Ship the build that you tested.
What changes
Only these three values change.Move to production
1
Register a production Seller account
Register at app.inflowpay.ai. This account is separate from your sandbox account.A Developer account cannot take payments. Seller calls from a Developer key fail with
403 SELLER_ACCOUNT_REQUIRED.2
Create a production API key
Create the key in the production dashboard. Store it in your deployment secret manager. Never commit it.
3
Set a production MPP secret
This step applies to MPP only. Generate a new secret.The secret must be at least 32 bytes. It must stay stable across deploys, because it signs and binds your
402 challenges. A change invalidates every challenge already in flight.4
Set the production environment
.env
5
Deploy the build you tested
Do not edit
server.ts. The same build reads the new values at startup.Check the live endpoint
1
Confirm the challenge
Call your live endpoint with no payment. Expect a
402 and the header of each protocol.2
Confirm what you advertise
3
Take one small live payment
Price one endpoint at your smallest amount. Pay it yourself with the CLI. This payment settles real money.
4
Confirm the settlement
For a stablecoin payment, open app.inflowpay.ai and confirm that the payment reached your InFlow balance. For a card payment, confirm the payment in your connected Stripe account. Confirm that the amount matches.
After you are live
- Publish your service to the directory. The directory has no sandbox, so this step needs your live origin. See Publish to the directory.
- Rotate your production key if you ever paste it outside your secret manager.
- Keep the sandbox deploy. Test every change there before you ship it.
Troubleshooting
For other errors, see Errors.
Next step
Check your integration
Test Payments, Enrollment, and Discovery against the live service.