Most fintech and web3 businesses that want to offer their users a card face the same choice: spend twelve to eighteen months securing a sponsor bank, building card issuance infrastructure, and setting up a separate KYC and compliance perimeter — or skip the product entirely.
UR's multicurrency card collapses that choice. Businesses looking to integrate an open financial structure to optimize money flow for both digital assets and fiat, or those that are already integrated with UR's account layer, can offer multicurrency Mastercard debit cards to their users. UR's card draws directly from balances held in 7 tokenized fiat currencies, all under UR's regulated perimeter.
This article focuses on UR's card layer, what partners get from integrating it, how the underlying multicurrency spending works for their users, and why the architecture matters for the partners.
What is the UR card?
The UR card is a Mastercard debit card tied directly to a user's account, facilitating the spending of 7 tokenized fiat currencies (EUR, USD, CHF, CNH, SGD, JPY and HKD). UR provides embedded Mastercard debit issuance to partners under its account layer stack, letting businesses offer their users a co-branded card funded directly from balances in the user's UR account.
UR is a principal Mastercard member and is a trademark of SR Saphirstein AG, a fintech company licensed under Article 1b of the Swiss Banking Act and supervised by FINMA. The UR card is accepted anywhere Mastercard is accepted — more than 100 million merchant locations globally, plus online — and it works with Apple Pay, Google Pay, Samsung Pay, WeChat Pay, and Alipay. As it is a module within UR's account layer rather than a standalone product, the same UR account that funds the card also holds the user's Swiss IBAN, supports SEPA, SWIFT, and SIC transfers, and includes on-ramp and off-ramp.
For the partner, this means the card is not a separate vendor integration on top of a separate custody integration that's on top of a separate compliance integration. It is one module of the same stack.
What are the benefits of integrating UR's card?
Integrating UR's card gives a partner a co-branded, principal-issued multicurrency Mastercard, that turns the user balances already on the partner's platform into spendable funds at over 100 million merchants — without the partner securing a sponsor bank, building issuance infrastructure, or extending its own compliance scope.
The card carries the partner's brand. It draws directly from each user's existing balances in the UR account, available in 7 fiat currencies, and lets the partner offer a flagship spending product on day one of launch instead of in a separate roadmap quarter. KYC, AML, transaction monitoring, sanctions screening, dispute handling, and network settlement all sit under UR, not the partner's.
The practical effect is that a wallet, exchange, neobank, or any platform whose users hold digital assets, including stablecoins, can launch a Mastercard program with the speed of a feature flag rather than the timeline of a massive project.
Which currencies can your users hold and spend on a UR-issued card?
Users hold and spend 7 tokenized fiat currencies — EUR, USD, CHF, CNH, SGD, JPY, and HKD — from the same UR account that funds the card, which also supports stablecoins and other digital assets.
Each tokenized fiat is a 1:1 deposit token, backed by the corresponding fiat held under UR's regulated perimeter. The card sees all of them as funding sources and can pull from any of them at the point of authorization. The 7 currencies cover the major payment corridors, especially in the markets where multicurrency users actually transact, receive income, or travel.
For the partner, this means a single card covers the cross-border use cases that would otherwise require multiple regional card partnerships.
How does multicurrency spending work for your users?
When the card is swiped or tapped, UR matches the merchant's local currency to a balance in the same currency if the user holds one, drawing from it directly at authorization. If no matching balance exists, UR converts from the most efficient available source at the network's rate, without forcing a base currency.
Partners do not need to build any of this logic themselves. The funding routing, FX path, and authorization handling are all handled inside UR's card module.
UR is a principal Mastercard issuer. Why does it matter for partners?
Being a principal issuer means UR is a direct member of the Mastercard network and the issuer of record for every UR card, rather than sitting behind a sponsoring bank — which removes the sponsor as a chokepoint in the partner's card program.
Some fintech and stablecoin card programs are sponsor-dependent. A sponsoring bank holds the network membership and the BIN; the fintech is the program manager; the cardholder relationship runs through a stack of three or more entities. That model is fast to launch but creates dependency on the sponsor's regulatory exposure, risk appetite, and continuity. The recent wave of BaaS disruptions, sponsor-bank consent orders, and partner-program freezes hit sponsor-dependent programs hardest because the chokepoint sat outside their control.
Principal issuance removes that chokepoint. UR sets program rules directly, holds the BIN, and settles directly with Mastercard. For the partner, this means the card program does not pause when a sponsor pauses, and does not have to be re-papered when sponsor relationships change. The user's card, account, custody, and compliance all sit inside one regulated perimeter.
How fast can a partner launch a co-branded card with UR?
Partners can launch a co-branded card program in weeks rather than the twelve to eighteen months typical of standing up a sponsor-bank card program from scratch, with UR's financial infrastructure and account layer.
The conventional path to a fintech card product runs through sponsor-bank selection, BIN allocation, program manager agreements, KYC and AML build-out, card production and fulfillment vendor selection, integration with a processor, and a regulatory readiness review. Even when each step goes smoothly, the cumulative timeline is measured in quarters.
With UR, the regulatory perimeter, the BIN, the processor, the FX engine, the custody layer, and the cardholder onboarding flow are already built. The partner integrates the module, configures branding and program parameters, and goes live. The card is the same Mastercard product the partner would have built; the work to assemble it is what disappears.
What does the integration look like — what does the partner build vs. what UR provides?
UR provides:
- The licensed infrastructure, issuance, custody, FX, compliance, and settlement
- The principal Mastercard membership, the BIN, and the named Swiss IBAN per user
- Custody of fiat and stablecoin balances, KYC and AML, transaction monitoring, sanctions screening, dispute handling, card production and shipping, network settlement, and the FX routing across 7 currencies
The partner provides:
- The user experience, the brand, and the user relationship
- The in-app surface where users see the card and manage spending, the onboarding flow, brand and card art, and the relationship with the end user
- Own spend controls, MCC rules, and notifications via the API (if applicable)
Crucially, the card is one of UR's account layer modules, not a separately licensed product. Partners that already use UR for IBANs, multicurrency custody, or rails do not take on a new vendor when they add the card; partners that start with the card can add the rest of the stack without re-papering.
Where can users spend the card?
Anywhere Mastercard is accepted — over 100 million merchant locations across more than 200 countries, both in person and online, plus Apple Pay, Google Pay, Samsung Pay, WeChat Pay, and Alipay.
Acceptance is identical to any other Mastercard, because the card is one. The difference sits behind the swipe: the funding source, the FX path, and the regulatory perimeter.
How is the card protected, and what does that mean for partner liability?
Every UR card is funded from the end user's own named Swiss IBAN, which means card balances are legally the user's property, segregated from UR's and the partner's assets, and protected under UR's regulatory perimeter rather than the partner's.
This is a structural difference from the typical fintech or crypto card. Most card programs run on omnibus accounts — a single pooled account in the operator's name, with user balances tracked on an internal ledger. UR's named-IBAN architecture means each user's balance sits in an account opened in that user's name. The bank, the regulator, and the network all see the user as the account holder of record.
The partner offers the card; UR carries the custody, the segregation, and the regulatory accountability. There is no chain of separate custodians, no nesting, and no dependence on a sponsor bank's solvency for the protection of card funds — which means there is no inherited solvency or compliance exposure for the partner either.
Who is integrating UR's card module today?
Wallets, exchanges, neobanks, payments apps, and platforms whose users hold digital assets — and who want to offer their users a spending product without building card issuance, multicurrency custody, or a sponsor-bank relationship themselves.
The common profile is a platform that has already aggregated user balances — fiat, stablecoins, or both — and wants those balances to function as real spending money rather than dead weight in an app. The card module turns that balance into a Mastercard product without the partner having to become a card issuer or expand its license. T
Why this architecture matters for partners
Card programs are usually evaluated on acceptance, FX margin, and fees. Those matter, but they describe the surface. The structural questions — who issues the card, where the balance lives, which currencies are native, what regulatory perimeter the program runs under, and what happens to user funds when something goes wrong — decide what the partner is actually signing up for over the lifetime of the program.
UR's card is one expression of a deliberate stack. For partners, that combination means a faster path to a card product, fewer vendors in the stack, no inherited sponsor-bank risk, and a custody architecture that keeps the user's funds out of both the partner's and UR's balance sheet. The card is what the partner ships; the architecture is what the partner stops having to build.
FAQ
Is the card fully co-branded with the partner's logo and brand?
Yes. Partners issue the card in their own brand, including card art, in-app naming, and cardholder communications. UR is the issuer of record under the hood, but the user-facing product is the partner's.
Who carries KYC and AML liability for cardholders?
UR carries it, as the licensed issuer of record. This includes KYC, AML, sanctions screening, transaction monitoring, and regulatory reporting. Partners do not have to extend their own compliance scope to cover the card program.
Can a partner use the card module without integrating the full UR account layer?
The card module is designed to sit on top of the UR account layer — the named Swiss IBAN, multicurrency custody, and compliance infrastructure are what make the card economics and protections work. Partners typically integrate the account layer as part of enabling the card, rather than separately.
How does this compare to using a sponsor bank directly?
Going through a sponsor bank means the partner likely manages the sponsor relationship, inherits the sponsor's risk appetite, and is exposed to any disruption at the sponsor level. With UR, the partner integrates one regulated counterparty whose card program is principal-issued, so there is no sponsor in the middle to manage, no sponsor risk to inherit, and no chokepoint outside the partner's or UR's control.
What happens if a UR cardholder spends in a currency they don't hold?
UR converts from the most efficient available balance at the network's rate, without forcing every conversion through a base currency.
