Card Switch
New card issued.
Every subscription updated.
Deck agents log into each subscription, handle authentication, and update the card on file so your card captures the spend.
Netflix
Spotify
Amazon
Uber
Built for card switching
Deck agents handle the full update flow across every platform your cardholders use. Authentication, navigation, and confirmation included.
No API partnerships needed
Deck doesn’t need a deal with every merchant. If a user can log in and update their card, Deck can too. Coverage is the entire web.
Authentication built in
Your user links their merchant account through your app. Deck stores the credentials, handles MFA, and establishes an authenticated session ready for the task.
Confirmed, not assumed
Every update is verified on the merchant’s site and returned with a confirmation timestamp. Failed updates surface the reason so you can act on them.
Store. Switch. Confirm.
Store your user’s merchant credentials, trigger the payment switch, and get confirmed results back.
{ "auth_method": "username_password", "auth_credentials": { "username": "[email protected]", "password": "••••••••" }, "source_id": "src_a1b2...", "external_id": "user_123" }
Store merchant credentials
Your user provides their merchant logins through your app. Store them in Deck Vault via the API. Keep them for future updates or delete on task completion. Your call.
{ "credential_id": "cred_a1b2...", "input": { "action": "update_payment_method", "merchants": ["all"] } }
Run the task
One API call runs the task. Deck agents log into each subscription, handle MFA, and update the payment method on file.
{ "status": "completed", "result": "success", "runtime_ms": 4523, "output": { ... }, "screenshots": [12], "reasoning": [8], "session_id": "sess_x9y8..." }
Get confirmed updates
Every task run includes structured output, screenshots, and agent reasoning artifacts. A full audit trail for every update.
Who’s this for?
Card issuers
When a new card is issued, Deck migrates every recurring payment automatically so users never experience failed charges.
Neobanks & wallets
Offer “switch all subscriptions to this card” as a first-class feature that drives card-on-file usage.
Subscription platforms
Let users update their payment method across every subscription from a single interface.
Expense management
When companies change card providers, Deck migrates every vendor subscription in parallel.
FAQ
Those platforms require merchant API partnerships, which limits coverage to whichever merchants have signed a deal. Deck operates through the browser. If your user can log in and update their card, Deck can do it programmatically. No partnership required.
Any merchant with a web login. Deck agents navigate real websites the same way a human would. There is no fixed merchant list or integration to maintain. Coverage scales with the web itself.
Every task run returns a structured result with status, error codes, screenshots, and agent reasoning. Your team gets the full context to decide whether to retry, notify the user, or escalate. Nothing fails silently.
Yes. Credentials stored in Deck Vault can be retained for future updates or deleted immediately on task completion. Your application controls the lifecycle through the API.
Most updates complete in seconds to a few minutes depending on the merchant site and any MFA steps involved. Task runs execute in parallel, so updating multiple merchants doesn’t mean waiting in sequence.
You can collect credentials however you want and store them via the API. Deck also provides an Auth Component you can embed directly in your app if you prefer a hosted flow. Either approach works.