Integrations
Stripe payment integration
FurlPay contains an optional Stripe PaymentIntent and webhook integration. A configured Stripe account, enabled payment method and deployment credentials are required. This page does not mean FurlPay offers a generally available fiat or crypto on-ramp.
Provider configuration is required
PaymentIntent route
| Method | Path | Description |
|---|---|---|
| POST | /api/payments/stripe/intent | Creates a USD Stripe PaymentIntent from a positive amount in cents; maximum $50,000 |
| POST | /api/webhooks/stripe | Verifies Stripe's signature over the raw event body and processes supported events |
The intent route validates amountInCents and accepts USD only. It returns a provider error when the Stripe integration cannot create the intent. Keep the returned client secret server-side until the approved Stripe client flow needs it; never log or expose a secret outside that flow.
Webhook requirements
- Register the exact endpoint and event types with the Stripe account used by the deployment.
- Set the corresponding webhook secret in the server environment; production fails closed if it is missing.
- Verify the
stripe-signatureagainst the raw body before processing. - Handle duplicate delivery idempotently and reconcile provider status before crediting an account.
Service availability
Stripe's product approval, payment-method availability, regional coverage, fees and settlement rules are determined by Stripe and the configured account. FurlPay does not guarantee that this integration is enabled in production. Check the service availability overview and the applicable provider dashboard before launch.