01
Setup
One-time. Covers environment, branding, configuration, integration support and launch rehearsal.
- Fixed on signature
- No hourly overrun billing
- Rehearsal included
Engagement
How a build actually runs.
The stack already exists and is already operated. Onboarding a partner is configuration, branding and rehearsal — not a greenfield engineering project with a moving date.
- Time to live
- 2 weeks
- Scope
- Fixed, written
- Support
- Named engineer
- Your data
- Exportable, always
- Day 0
First conversation
What you want to launch, which market, which licence you hold or are applying for, and the date you need to be live.
- Day 1–3
Build plan
We return a written scope: asset classes, corridors, methods, branding surface, integration points, and a fixed launch date. Not a proposal deck.
- Week 1
Environment stood up
Your dedicated environment provisioned. Domains, certificates, branding applied. Sandbox credentials issued to your developers on day one, not at the end.
- Week 2
Configuration and rehearsal
Instruments, pricing, limits, payment methods and compliance tiers configured with your team. Full rehearsal against sandbox including a payout run.
- Launch
Live under your brand
Cutover with us on the call. No Krexum badge, no footer credit, no shared brand anywhere your customer can see.
- Ongoing
Operated
Monitoring, incident response, security patching and roadmap delivery continue as one relationship. You get a named engineer, not a ticket queue.
Launch sequence
Nine phases, and we tell you which one is the long pole.
Most vendor timelines draw every phase the same width, which is how a partner discovers in month three that provider onboarding was never going to fit in week two. Ours is marked. It starts on day one and runs underneath everything else, because the honest version is the one you can plan around.
Scoping
Day 1We do
We ask what market you are entering, what licence position you hold or are pursuing, which products you need and what date you are working to. We say at this point if something is not workable.
You do
One conversation and a decision-maker in the room.
What exists after
A shared, written understanding of what is in scope — and what we have told you is not.
Build plan
Within 3 working daysWe do
We write the plan: architecture, product configuration, every dependency with the date it is needed, the commercial shape, and a fixed launch date we are willing to be held to.
You do
Read it and challenge the date.
What exists after
A costed plan with a fixed launch date, at no cost and with no retainer.
Provider onboarding
Starts day 1, runs underneath everythingThe long poleWe do
Introductions to acquirers, sponsors, liquidity and banking partners, and we carry the technical side — applications, BIN sponsorship, scheme certification.
You do
Corporate documents, director information and underwriting responses. This is where partners lose weeks, and it is the one part we cannot do for you.
What exists after
Approved provider relationships. This is the longest pole in the tent, which is why it starts before anything is built rather than after.
Environment
Week 1We do
A dedicated, isolated environment provisioned in the region that matches your licence and your supervisor. No shared database, no shared credentials.
You do
Confirm the data-residency requirement your regulator imposes.
What exists after
Your environment, running, with monitoring and backups configured.
Brand & configuration
Week 1–2We do
Your brand applied across every surface — platform, console, statements, transactional email, payment pages, cards, domain. Products, instruments, fees, leverage, rules and limits configured to your model.
You do
Brand assets and sign-off on the configuration.
What exists after
A platform that looks like yours because it is yours. Krexum appears nowhere a customer can see.
Integration & sandbox
Week 2We do
Sandbox with test credentials, simulated settlement and test card issuance, so your team integrates against something real before anything is live.
You do
Any integration into your own systems — CRM, warehouse, accounting.
What exists after
Verified API, webhook and reconciliation contracts.
Rehearsal
Before cutoverWe do
A full dry run: deposits, trades, withdrawals, payouts, reconciliation, breach detection, and a deliberate provider failure to prove the failover works.
You do
Your operations team runs it, not us. If they cannot, you are not ready.
What exists after
A rehearsed team and a list of anything found — fixed before launch, not after.
Cutover
The fixed dateWe do
Go live, with engineers on point through the window rather than reachable in theory.
You do
Say go.
What exists after
Live, under your brand, on the date in the plan.
Operation
OngoingWe do
We run it: monitoring, patching, incident response, reconciliation, corridor and provider additions as configuration. A named engineer who knows your deployment.
You do
Run your business.
What exists after
Incident history shared with you rather than hidden behind a status page.
Two weeks describes the build. Provider approvals and any authorisation you are pursuing run on their own clocks, which we do not control and will not pretend to. The plan states which of your dates depend on someone else’s decision.
Commercials
Priced so you can model it.
Setup plus a monthly platform fee, with transaction economics that scale as you do. Exact numbers depend on scope, corridors and volume — these are the shapes, and we quote firm before you commit.
02
Platform licence
Monthly, by tier. Covers the whole stack, operations and support — not per module.
- No per-layer pricing
- Support included
- Roadmap access included
03
Transaction economics
Payment processing and card economics priced per corridor and method, disclosed in full.
- Per-corridor pricing
- Disclosed FX margin
- No blended-rate opacity
Terms
The things partners are right to ask about.
- Do you compete with us?
- No. We do not run a consumer brand in your market and we do not sell to your customers. If that ever changes we will tell you before it does, not after.
- Will you name us?
- No. We do not publish partner names or logos. A vendor that advertises its clients is telling every future client it will advertise them too.
- Who owns the data?
- You do. Full export in documented formats on request, during the relationship and on exit.
- What if we outgrow the tier?
- Tiers move with volume. Growing is not a renegotiation event.
- What if we want to leave?
- Documented exit: data export, a transition window, and no hostage-taking on your customer records.
- Who do we call at 3am?
- A named engineer who knows your environment, through an agreed escalation path with defined response times.
Start
Send us the market and the date.
We come back within three working days with a written build plan and a fixed launch window.