About Us

Immersve is a global card-issuing payment institution and principal partner of Mastercard, built to make digital assets spendable in real time on the Mastercard network. We power some of the largest crypto card programs in the world, including Binance, KuCoin, Bitget Wallet and MetaMask; with no bank and no fiat rail involved. We own the full stack, end to end.

Money is evolving. Its moving onchain faster than most financial systems can keep up with. Stablecoins settle in seconds, run around the clock, and don't care about time zones or banks. Immersve is the last mile: the bridge between web3 infrastructure and the Mastercard acceptance network; turning stablecoin balances into money people can spend today, everywhere Mastercard is accepted.

Our partners don't have to teach their users a new way to pay. We handle the plumbing so the experience feels exactly like the one people already know. Even works with Apple and Google Pay.

The next wave of financial institutions won't win by asking customers to change their habits, they'll win by rebuilding what's underneath while everything on the surface stays familiar. That's the problem we're solving at Immersve, and why we're hiring people who want to build it.

Why this role exists

Immersve lets crypto and fintech companies issue Mastercard cards backed by on-chain funds. Our partners bring the users and the wallet. We bring the card programme, the issuing and scheme relationships, and the compliance framework behind them.

Getting a new partner from signed contract to first live transaction is a critical process. It runs across compliance, technical integration and brand work in parallel, and it involves Mastercard, regional issuers, our platform, and the partner's own engineering and compliance teams.

We are growing the number of partners we onboard each year, and we are building a dedicated team to run it. You are the technical half of that team.

What the job actually is

🛠️ Configure our side: Every partner needs their programme set up in our platform, first in test and then in production. Card products, funding, KYC configuration, fees, credentials, spend controls. You own that configuration and its correctness.

🤝 Be the partner's technical counterpart: From the moment integration starts you are the person their engineers talk to. They will ask why a test transaction declined, how the funding flow behaves, what our webhooks do on retry, and why a card did not provision into a mobile wallet. You answer, or you find out and then answer.

🗝️ Prove it works: Before a partner goes live they pass a technical certification: a defined set of flows exercised end to end, evidenced and signed off. You run it.

🔎 Debug across a deep stack: A single declined authorisation can come from configuration, the card scheme message, a compliance status, an on-chain balance, or the issuer. Working out which, quickly, with a partner watching, is a large part of the job.

🔦 Own the quiet prerequisites: The technical groundwork that holds a launch up when it is assumed rather than assigned. You track it and you chase it.

⚙️ Automate the repetitive parts.

The part that makes this different

We are an AI-first company and we mean it operationally, not as marketing.

Much of the setup work above follows a process and is currently manual. We are not hiring someone to do it faster by hand. We want someone who turns it into tooling and agent skills, so that it becomes repeatable and reviewable, and eventually something partners can drive themselves.

That means you should be comfortable scripting against APIs, working with coding agents as a normal daily tool, and treating your own runbook as something to replace rather than protect. If your instinct on seeing a long manual process is to follow it carefully every time, this is not the right role. If your instinct is to do it once and then write the thing that does it, we should talk.

Your first ninety days

Weeks 1 to 4: Learn the product by using it. Set up test programmes, issue cards, run transactions, break things in the sandbox.

Weeks 4 to 8: Shadow a live partner integration. Sit in the channel, answer what you can, escalate what you cannot, and note every question you had to escalate.

Weeks 8 to 12: Own an onboarding end to end, and ship the first piece of automation that removes a step you have now done by hand more than twice.

What we're looking for

Necessary

You have been the technical person facing a customer or partner during an integration, and you are comfortable being the one they message when something is broken;
You are fluent with REST APIs and webhooks, and with debugging an integration you did not write: logs, request traces, reproducing a failure from someone else's description;
You can write and maintain scripts. Python, TypeScript, Go, whatever. This is not a software engineering role, but code is a tool you reach for without hesitating;
You write clearly. Much of your output is written explanation to people who cannot see what you can see;
You are organised without being told to be. Several partners will be in flight at once, each waiting on something different.

Helpful

Payments experience: issuing, processing, scheme rules, 3DS, tokenisation;
Crypto experience: wallets, custody models, stablecoins, approvals, differences between chains;
Exposure to KYC and KYB tooling and the flows around them;
Experience building internal tooling or automation for an operations team.

Not required

A computer science degree;
Deep knowledge of both payments and crypto. Most people have one. We can teach the other, and we would rather hire for judgement and debugging instinct than for prior exposure to a checklist of technologies.Describe the ideal candidate here.

Some of our perks

Flexibility - Work from anywhere in NZ for that perfect work-life balance and 5 weeks Annual Leave ⚖️
Support - People first approach 💗 with investment in personal growth, ongoing learning and development 📚
Reward - Competitive salary and share options 📈
Technology - MacBook Pro (Silicon 🤩) and a home office budget ⌨️

Application Process

2 interviews + 1 practical challenge.

First is a general interview, then the practical task (an interesting technical challenge).

We’d love to hear from you! Please send your CV to careers@immersve.com.

At this stage, we are only considering candidates who are currently based in New Zealand and have valid working rights in New Zealand.

We look forward to hearing from you!

Immersve

New Jobs

Partner Solutions Engineer