The proxy enforces several constraints to protect your backend and prevent abuse. This page covers what's blocked, why, and how to work within these limits.
HTTPS requirement#
Your backend URL must use HTTPS. The system rejects HTTP URLs at both the database and application level.https://api.example.com - Allowed
http://api.example.com - Rejected
For local development, use an HTTPS tunnel:This gives you a public HTTPS URL that forwards to your local server.
Security restrictions#
The proxy enforces security restrictions to protect both your backend and our infrastructure. These restrictions ensure your proxy service operates securely and reliably.
Request limits#
| Constraint | Limit |
|---|
| Request body size | 64KB maximum |
| Upstream timeout | 50 seconds |
| Protocol | HTTP/HTTPS only (no WebSocket) |
If your use case requires larger request bodies or WebSocket support, use the Standard SDK instead.
Redirect blocking#
The proxy blocks all 3xx redirects from your backend for security reasons. If your backend returns a redirect, the proxy returns a 502 error to the client.If your backend uses redirects internally, resolve them before they reach the proxy endpoint.
Domain verification#
Domain verification adds a layer of protection to the proxy:You can only proxy domains you've verified ownership of
Verifying example.com allows api.example.com and all subdomains
Verifying api.example.com doesn't cover example.com, and lookalike hosts such as example.com.evil.net never match
Each service's base URL and each route's target URL are validated against your verified domains
A domain that isn't verified within 7 days of being added expires; add it again to get a new token
Payment security#
Server-side requirements#
The proxy always determines payment requirements (amount, asset, recipient wallet) server-side from your configuration in the database. It never trusts client-provided values.This means clients cannot:Manipulate the payment amount
Redirect payments to a different wallet
Change the usage model or limits
Before forwarding requests to your backend, the proxy removes payment-related headers and optionally injects your upstream authentication key.Your backend receives clean requests with no payment tokens or signatures.
Data isolation#
All proxy configuration is scoped to your account:Domains - Only you see your verified domains
Services - Only you see your services
Capabilities - Only you see your enabled capabilities
Routes - Only you see your route overrides
No other merchant can access or modify your configuration.
Audit logging#
All proxy configuration changes are logged for security and compliance purposes.
Next steps#
Modified at 2026-10-21 21:00:51