UP Gateways Release 2026.10.808
⚠ 11 breaking changes AuthCapture IDs and follow-up errors have changed · Batch file access now needs specific permissions · Merchant contact details now reject invalid email and phone formats · User lists now show only your own scope · User lookup and changes now respect account scope · Merchant credentials can no longer read other merchants' names · User creation and updates now enforce role and reseller checks · Wallet registration reads are now access-limited · Settlement run-state now requires MerchantId and RunId · Wallets no longer collect shipping addresses in locked sessions · API reference now shows the correct response content types
- Hosted payment page (3)
The Hosted Payment Page now supports shopper-selected carrier shipping rates, and wallet-based shipping flows are more accurate when shipping is locked or already chosen. - Virtual Terminal (3)
The Virtual Terminal now supports more transaction details, including register selection, duplicate-check waiver, soft descriptor, notes, and tags. - Fraud controls and security (3)
Transaction screening now supports more rule types, including per-card, per-device, IP, email, decline-rate, country, and time-of-day checks, with local holds and better handling of retry and repeat declines. - Transaction operations and settlement (3)
Transaction Explorer now gives a fuller view of settlement and approval activity, including partial approvals, all settlement statuses in filters, and a settlement remediation queue for retrying affected batches. - Back-office reporting and workflows (3)
Contract management now supports bulk operations, CSV import, and change history, making large contract updates easier to manage. - Admin UI and dashboards (3)
Grids across the admin UI now have a more capable filtering experience, with an All filters drawer, collapsible filter cards, better range controls, clearer validation, and improved handling of saved or refused filters. - Developer portal and API reference (3)
The API reference now shows richer operation details, including accurate response media types, examples, enum members, nested fields, model pages, required scopes, and published request examples on operation pages. - Access controls and data handling (3)
Several merchant, user, wallet, and hosted-session reads are now more tightly scoped so users only see records they are allowed to access.