NXT Enterprises

Audience: Devs, Support, SRE, Finance Outcomes: Ship fast; resolve issues calmly

<code>POST /api/payments/intents</code> with <code>orderId</code>

Stripe webhook <code>payment_intent.succeeded</code>

Handler updates payment; emit <code>payment.succeeded</code>; set DepositPaid

1. <code>POST /api/payments/intents</code> with <code>orderId</code>
2. UI completes SCA via Elements
3. Stripe webhook <code>payment_intent.succeeded</code>
4. Handler updates payment; emit <code>payment.succeeded</code>; set DepositPaid
5. SSE updates UI → start work

<code>POST /api/payments/bank/link</code> → provider URL

Mark DepositPaid; SSE notifies participants

1. <code>POST /api/payments/bank/link</code> → provider URL
2. Buyer completes auth; returns to app
3. Provider webhook confirms settlement
4. Mark DepositPaid; SSE notifies participants

<code>POST /api/escrow/release</code> (<code>orderId</code>, <code>milestoneId</code>, <code>amount</code>)

Monitor on-chain tx; emit <code>escrow.released</code>; update invoice

1. <code>POST /api/escrow/release</code> (<code>orderId</code>, <code>milestoneId</code>, <code>amount</code>)
2. Monitor on-chain tx; emit <code>escrow.released</code>; update invoice

POST /api/webhooks/stripe POST /api/webhooks/bank

POST /api/payments/intents POST /api/payments/stripe/checkout-session POST /api/payments/bank/link

POST /api/escrow/deploy-contract POST /api/escrow/monitor-deployment POST /api/escrow/release

Stripe <code>card_declined</code> → <code>PAYMENT_FAILED</code>

Bank <code>invalid_signature</code> → <code>WEBHOOK_INVALID_SIGNATURE</code>

Crypto <code>insufficient_gas</code> → <code>ESCROW_RELEASE_FAILED</code> UX: translate to human messages; include provider references for support.

- Stripe <code>card_declined</code> → <code>PAYMENT_FAILED</code>
- Bank <code>invalid_signature</code> → <code>WEBHOOK_INVALID_SIGNATURE</code>
- Crypto <code>insufficient_gas</code> → <code>ESCROW_RELEASE_FAILED</code> UX: translate to human messages; include provider references for support.

Check provider logs → replay; verify signature → check handler dedupe; reconcile manually with note if needed.

- Check provider logs → replay; verify signature → check handler dedupe; reconcile manually with note if needed.

Throttle workers; verify DB indexes; ensure idempotency; drain queue, then restore limits.

- Throttle workers; verify DB indexes; ensure idempotency; drain queue, then restore limits.

Disable proxy buffering; confirm CORS + credentials; inspect long-lived response closures.

- Disable proxy buffering; confirm CORS + credentials; inspect long-lived response closures.

P1 money wrong recipient → on-call engineer + finance lead + exec

P2 delayed confirmations → SRE + support

- P1 money wrong recipient → on-call engineer + finance lead + exec
- P2 delayed confirmations → SRE + support

After incident replay, no duplicate releases (idempotent handlers)

All journal entries tie to <code>orderId</code>, <code>invoiceId</code>, and provider references

- After incident replay, no duplicate releases (idempotent handlers)
- All journal entries tie to <code>orderId</code>, <code>invoiceId</code>, and provider references

Copy-paste flows, core endpoints, and step-by-step incident handling.

Recipes, API Quick-Ref & Runbooks

Find answers and get help from Intercom Support and Community Experts

This site employs cookies and other technologies that we and our third party vendors use to monitor and record personal information about you and your interactions with the site (including content viewed, cursor movements, screen recordings, and chat contents) for the purposes described in our Cookie Policy. By continuing to visit our site, you agree to our {websiteTermsLink}, {privacyPolicyLink} and {cookiePolicyLink}.

This site uses cookies and similar technologies ("cookies") as strictly necessary for site operation. We and our partners also would like to set additional cookies to enable site performance analytics, functionality, advertising and social media features. See our {cookiePolicyLink} for details. You can change your cookie preferences in our Cookie Settings.

We use cookies to make our site work and also for analytics and advertising purposes. You can enable or disable optional cookies as desired. See our {cookiePolicyLink} for more details.

Advertising cookies are set by our advertising partners to collect information about your use of the site, our communications, and other online services over time and with different browsers and devices. They use this information to show you ads online that they think will interest you and measure the ads' performance. Social media cookies are set by social media platforms to enable you to share content on those platforms, and are capable of tracking information about your activity across other online services for use as described in their privacy policies.

These cookies enable the website to provide enhanced functionality and personalisation. They may be set by us or by third party providers whose services we have added to our pages. If you do not allow these cookies then some or all of these services may not function properly.

These cookies are necessary for the website to function and cannot be switched off in our systems.

These cookies allow us to count visits and traffic sources so we can measure and improve the performance of our site. They help us to know which pages are the most and least popular and see how visitors move around the site.

You have the right to opt out of the sale of your personal information. See our {cookiePolicyLink} for more details about how we use your data.

Your Privacy Choices

We use cookies to enhance your experience. You can customize your cookie preferences below. See our {cookiePolicyLink} for more details.

Cookie Settings

Link, Press control-option-right-arrow to exit

Empty Help Center

Uh oh. That page doesn’t exist.

Disappointed

Neutral

Smiley

Thinking...

Searching through sources...

Analyzing...

Tickets submitted through the messenger or by a support agent in your conversation will appear here.

Recipes, API Quick-Ref & Runbooks

End-to-end recipes

API quick-reference

Error mapping (provider → platform)

Incident runbooks