Skip to main content
This article answers common questions from customers migrating from Widgets to UX Toolkit (UXT). If your question isn’t covered here, contact your Marqeta Account Manager.

​
Does UX Toolkit support all the features that Widgets did, or are there gaps?

UX Toolkit offers feature parity with Widgets, while adding capabilities. Card activation, PIN set and reveal, and card display all carry over. UX Toolkit also adds capabilities Widgets didn’t offer, such as freeze and unfreeze, card replacement, transaction history, account balances, dispute filing, account funding, statements, and user onboarding.

​
Does UX Toolkit support the same card products and programs we’re currently using?

Yes. UX Toolkit supports the same card products and programs you use today.

​
Can the same theme be used for multiple programs?

Yes, but you must upload it separately to each program. The same theme JSON can be reused across programs, but you upload it to each program individually through the /theme endpoint, using that program’s own credentials. After you upload the theme, each program’s bootstrap() call references it by themeName. For additional information on applying themes see the UX Toolkit documentation.

​
Is a mobile native SDK coming?

A mobile native SDK is on the roadmap. Development is planned to begin with React Native card components, with Swift and Kotlin SDKs to follow.

​
How much development effort is required to migrate?

Most customers complete a full implementation in 1–2 weeks. Some customers have completed migration in as little as four days.

​
Is there a migration guide?

There is no explicit migration guide as you are not migrating your widgets but rather leveraging the current UX Toolkit. See the UX Toolkit Getting Started guide for step-by-step setup instructions on getting started.

​
Can we run Widgets and UX Toolkit in parallel during the transition?

Yes. Widgets and UX Toolkit can run concurrently for a two-week testing window, so you can validate system stability before you complete the migration.

​
Can one Customer Authentication API be used for multiple programs?

Yes, but each program still needs its own OAuth client and key pair. You can use a single Customer Authentication API service to support multiple card programs, but you must register a separate OAuth client and key pair for each program and environment. The Marqeta platform doesn’t support reusing a key pair across programs, or between sandbox and production. For more information about registering OAuth clients, see the Customer Authentication API documentation.

​
Does the short code for your card program stay the same from sandbox to production?

Yes. Your program short code stays the same across your sandbox and production environments.

​
Are there costs associated with UX Toolkit?

UX Toolkit is free to use until your contract renews. At renewal, contact your Account Manager to discuss pricing for your program.

​
Can themes be hosted locally?

No. The Marqeta platform hosts themes remotely. You can’t download a theme once you upload it, and the Marqeta platform doesn’t retain a version history of your theme’s JSON file, so keep a local copy of any theme you build in Studio.