Ramp Widget — v1 Shutdown
Action required — Widget v1 stops working on 30 October 2026On 30 October 2026, Ramp Widget v1 will be switched off. Any integration that still launches the widget with customer or order details in the URL will stop working on that date. If you haven't migrated to Widget v2 yet, you need to do so now.
Summary
Widget v2 was released in July 2026 and has been the recommended integration path since then. To keep the widget secure and maintain a single integration path, we are now shutting down the legacy v1 integration.
30 October 2026 is a hard cut-off, not a soft deprecation. After this date, v1 widget launches will fail.
Key dates
| Date | What happens |
|---|---|
| 17 July 2026 | Widget v2 released to production. Migration recommended for all customers. |
| Now | Final window to migrate. Widget v2 is fully available in sandbox and production. |
| 30 October 2026 | Widget v1 is switched off. v1 URLs will no longer launch the widget. |
What's changing
| Widget v1 (shutting down) | Widget v2 (current) | |
|---|---|---|
| How you launch | Client-side redirect with apiKey, customer and order details, and signature in the widget URL | Backend calls POST /v2/ramp-session, then redirect the customer to a URL containing only a sessionId |
| API key | Exposed in the browser URL | Sent as a header from your backend only |
| Request integrity | signature query parameter | HMAC-SHA256 over the session-creation request |
| Data in browser URL | Full order and customer details | Opaque, single-use sessionId only |
| Status after 30 Oct 2026 | ❌ Stops working | ✅ Supported |
What you need to do
If you have already migrated to Widget v2, no action is needed.
If you are still on v1:
- Confirm you're affected. If your integration redirects customers to the widget with
apiKey, order or customer details as query parameters, you are on v1. - Set up your v2 prerequisites in the dashboard — generate your HMAC secret and add your backend egress IPs to the allow-list (required; session creation is rejected from non-whitelisted IPs).
- Move session creation to your backend. Call
POST /v2/ramp-sessionwith the same details you currently pass in the URL. You'll receive asessionIdandredirectUrl. - Redirect the customer to the returned
redirectUrlinstead of building the widget URL yourself. - Test in sandbox, then go live before 30 October 2026. Sandbox and production use separate HMAC secrets.
The parameter-by-parameter mapping from v1 query params to v2 session fields is in the v2 release notes linked below.
Resources
- 📖 Widget v2 Integration Guide — full migration and integration walkthrough
- 📝 Widget v2 release notes — API reference, signing scheme, v1 → v2 field mapping, and troubleshooting
Need help?
- Email [email protected]
- Message us on your dedicated Slack channel (link available in your Customer Dashboard)
- Or reach out directly to your TransFi account contact
If you expect to miss the 30 October deadline, contact us before the cut-off so we can plan around it.