transaction:deposit-e2e flow handles the entire card deposit in one session: the user picks the destination Uphold account, links or selects a card, enters the amount, reviews a live quote, completes any 3DS challenge and confirms the status of the transaction — all without your backend creating a quote or a second session.
If you need to build the amount entry and review screens yourself, see Transaction - Select Deposit Origin instead. To compare all flows, see Flows.
Prerequisites
- The user has completed onboarding and has the required capabilities enabled.
- The Payment Widget is set up in your frontend. See Installation and setup.
@uphold/enterprise-payment-widget-web-sdkis on a version that supports the end-to-end flows.
Walkthrough
Complete the deposit in the widget
The widget session takes the user from account and card selection through the amount, quote and authorization.Create a widget session
Call Create widget session to start thetransaction:deposit-e2e flow. No data is required — the widget gathers everything from the user. Use options to customize the Widget’s theme and layout, as well as the flow itself. See Create a session and the SDK reference for all available options.
By default, the end-to-end flows offer bank, card and crypto. To offer card only, set paymentMethods to card:
session object with a url field that loads the widget. Return response.session to your frontend as is.
Set up the widget
Both examples above are for web applications — either creating the iframe yourself or letting the SDK do it. For native apps using a WebView, see Native apps with the Web SDK for the SDK’s native-bundling pattern, or Setup without the SDK for the no-SDK approach that loads the session
url directly as the WebView’s top-level page.Handle the complete event
Thecomplete event fires when the user closes the terminal status screen. Its value is the authorization result — the transaction plus what triggered the completion.
The handlers below assume a card-only session. If your session also offers bank or crypto, those deposits complete with
via: "deposit-method" and no trigger — handle that case first. See Bank deposit (End-to-end) and Crypto deposit (End-to-end).external-account representing the card and the destination is the user’s account.
Handle cancellations
Thecancel event fires when the user closes the widget before authorizing. No transaction exists at that point.
Handle errors
The widget recovers from quote and authorization failures internally by returning the user to the review screen with an appropriate action — change the amount, change the payment method, or try again. Theerror event is reserved for failures the widget cannot recover from.
Monitor for settlement
Card deposit transactions may remain inprocessing while the payment settles. Monitor until the transaction reaches a terminal state.
- Webhook events (recommended):
- core.transaction.created —
status: processing→ transaction created, pending settlement - core.transaction.status-changed —
status: completed→ funds settled;status: failed→ irrecoverable error
- core.transaction.created —
- Polling (fallback): Get transaction
Notify the user
Display an in-app confirmation when the transaction iscompleted, and send an email if applicable.
You now support end-to-end card deposits via the Payment Widget.