Quotation

VaultaPay — Omniom quotation

10 October 2026·Prepared by Ivan James·Omniom AI Limited

Summary

We would build an admin back office for your team, a client portal for your customers, and the VaultaPay website — all reading and writing through the ONE.io API, and all built on the Omniom platform.

ONE.io becomes your system of record: accounts, payments, balances, statements and custody stay with them. Omniom provides the back office, client portal, web builder and communications as modules that already exist, so most of this engagement is configuration and integration rather than development from scratch. That is what makes it quick, and it is what makes it affordable.

It is also a deliberately smaller job than replacing Swiss Fiat. We are not rebuilding a bank. We are building the interface to one.

The first stage is a paid discovery that maps every ONE.io capability to a screen and settles the handful of questions their API documentation leaves open. Everything after it is fixed price per stage.

What we reviewed

We have been through the ONE.io sandbox and its API documentation, the Swiss Fiat administration system, and the VaultaPay website and client area.

Swiss Fiat is a well-built system and it has told us a great deal about the shape of the admin screens your team actually uses. But it is somebody else's platform, running somebody else's product set, and most of what sits inside it — card issuing, personal customer verification, the fee matrix, the AML case workflow — is not what you are buying. Treating it as reference rather than as a migration source is what keeps this project small.

The model

Today you are an affiliate inside Swiss Fiat's system, operating under their arrangement and in their database. On ONE.io you become the account holder, and your clients become subsidiary organisations beneath you.

ONE.io holds the money and the record. Omniom holds the experience.

That split is the whole design, and it is worth being precise about it.

We store no customer identity documents and no verification data. That stays with ONE.io, which removes a whole category of obligation from you and is the main reason the platform licence below is as modest as it is.

Clients are corporate only — subsidiary organisations under your master account. The personal customer product does not carry across, and nothing in this quotation assumes it will.

Scope of work

Every ONE.io capability maps to a screen in your admin back office, a screen in the client portal, or both. This is that map.

Alongside the map, four things that are ours rather than ONE.io's.

Staff and permissions. Admin users, roles and what each role can see and do, with a full audit trail of who acted on which client.

Client onboarding journey. From enquiry through to a provisioned, allocated, usable account — including whatever verification step the answer to question 1 below requires.

Communications. Around 15 to 20 email templates carried across from Swiss Fiat and rebuilt in your own system, the automations that trigger them, and messaging between your team and your clients.

Website. The VaultaPay site rebuilt in the Omniom web builder, carrying existing content, with portal sign-in from it.

Two pieces of engineering worth naming

These are not obvious from a feature list and they are where a careless build goes wrong.

Payment reconciliation. The Faster Payments and SEPA endpoints carry no idempotency key — only crypto withdrawals do. A request that times out cannot simply be retried, because it may already have sent. Every payment submission is therefore checked against the transaction list before any retry. Without this, a network blip sends money twice.

Token handling. Every call carries a one-hour JWT and a separately encrypted partner token identifying the acting user, and when you act for a client it also carries that client's subsidiary ID. All of it is built server-side, never in the browser, and every call is logged against the client it was made for.

Stages

Each stage ends where the work is usable and the engagement could be paused. Nothing in a later stage starts before the previous one is signed off.

Crypto custody sits in stage 2 or 3 depending on the answer to question 5. The Talos trading integration is not in this scope — see Not included.

Platform licence and environment

The build runs on Omniom, which carries an annual licence. The licence is per instance, not per user — adding staff never adds cost, and there is no per-seat charge at any point.

That includes shared hosting, platform upkeep, support, all core platform updates released in the licence period, unlimited users, and 10 GB of managed data.

10 GB is comfortable here precisely because of the model. Balances, transactions and statements are read from ONE.io rather than stored, and no identity documents are held at all. What Omniom stores is records, messages and templates, which are small. A platform holding verification documents would need five times the allocation and a larger licence.

If that changes, the Growth tier at £2,100 includes the same three modules and 50 GB. It is £200 more and is the natural step if document storage ever comes in scope.

Dedicated environment — from £900 a year, quoted. Shared hosting is included above and gives you your own instance and your own database on shared infrastructure. If your own compliance position or ONE.io's certification requires dedicated hardware or a named jurisdiction, that is a quoted upgrade and is worth settling during discovery rather than after launch.

The licence is published in full at omniom.ai/pricing, is invoiced annually in advance, and renews at the then-current list price. It is not discounted — any concession attaches to the implementation fee instead.

The ONE.io integration is specific to you rather than a standard platform feature. We maintain it under the licence for the first licence period and review it with you at renewal.

Metered services

Some things cost money every time they are used, and we charge them on rather than build them into the licence. The rule is provider cost: if a supplier bills us for it, it is metered at their cost plus 20%. If nothing external bills, there is no charge.

These cannot be quoted in advance, because they depend entirely on your volumes. What we can tell you is that every send shows its exact cost on the button before it goes, and every message carries what it cost on the record afterwards. There is no end-of-month surprise, by design.

Usage reserve. Metered services are funded in advance from a reserve, set at six weeks of projected usage and topped up when it falls below fourteen days of your actual run rate. We size the initial reserve during discovery, once we know your message and verification volumes. If the reserve runs out the meter pauses — the platform keeps running. Any unused balance is refunded if you leave.

Cost

All figures ex VAT. VAT is applied according to where the invoice is raised and to which entity, confirmed before the first invoice.

Year two onward is £1,900 a year plus whatever you consume in AI and messaging. There is no second implementation fee and no per-user charge. We state the renewal figure here rather than let it arrive as a surprise twelve months in.

The implementation price is my estimate of the hours this takes, less 30%. At standard rates this scope would be quoted higher; what brings it to this level is set out under the referral/partner scheme below, and it is worth both parties being explicit about it.

Each stage is fixed price. We carry the risk of our own estimate inside a stage.

Changes. Anything outside the specification agreed at the end of stage 0 is quoted as a fixed-price addendum and started only once you have accepted it. Nothing is added to an invoice without that.

Budget allowance. We would suggest you hold a further £3,000 in budget against changes that emerge once ONE.io's answers to the five questions land. It is not committed, it is not invoiced unless you accept a specific addendum, and on a well-run discovery it should not be needed in full.

Referral/partner scheme

Omniom’s core structure is built for vertical, industry-specific platforms, assembled from applications and prebuilt functions rather than written from scratch. That makes the experience gained building VaultaPay directly reusable for other businesses that want to work with ONE.io and see the value of having every function in one place.

That is why this build is priced around 30% below normal developer rates. The work has value to Omniom beyond this engagement, and the reduction is what you get for it.

It also creates the opportunity for a partner commission scheme. The benefits are already set out at omniom.ai/partner, and terms would be agreed with you separately.

How that could work for you. ONE.io and VaultaPay came together through you, and the same is likely to be true of the next few. As an affiliate you introduce and take a commission on what they sign. As a partner you sit in the deal itself and take the margin, which can run through a business set up for the purpose rather than through VaultaPay. Which of the two fits is worth settling once the first one appears rather than now — either way it is income from work you are already doing.

Your own data, content, branding and configuration remain yours alone and are never reused.

Worth a conversation. Have a look at the partner page and let’s talk it through. Nothing here needs deciding to get stage 0 moving, and none of it changes the price above.

Open questions

Five questions remain, and they are for VaultaPay and ONE.io rather than for us. Each is drawn from ONE.io's own documentation, which names most of them as gaps. Closing them is the substance of stage 0, and we would rather put them in front of you now than discover them halfway through a build.

1. Who verifies a new client organisation? ONE.io's integration notes put onboarding and KYC for new sub-accounts out of scope and record that nothing documents whether a subsidiary needs its own verification. If ONE.io handles it, Sumsub leaves the journey entirely. If VaultaPay handles it, Sumsub stays and the handoff needs designing. This is the one that most changes the build.
2. Does the partner key need reissuing per client? Their documentation says delegated access works “as configured in the partner auth key.” If a key must be issued for each subsidiary, client provisioning cannot be self-service and someone at ONE.io is in the loop on every new client.
3. How do clients fund their accounts? There is no funding endpoint in the published specification. ONE.io identify this themselves as the main unknown in their own integration work.
4. Does VaultaPay add a margin on ONE.io's fees? If fees are passed through, we display the fee transaction their API already returns. If you mark them up, there is a pricing and billing layer to design and build, and it is not trivial.
5. Is crypto custody in phase one? Deposit addresses, whitelisting and withdrawals are straightforward REST calls. Including them is a modest addition; excluding them removes a stage-2 item.

Assumptions

• ONE.io sandbox credentials, the partner key and API access are available to us at the start of stage 0.
• ONE.io's production certification, which checks that calls match their specification, can be scheduled to meet the launch date. It is their gate, not ours.
• No customer data is migrated from Swiss Fiat. Existing clients are onboarded onto new accounts.
• Website content carries across as it stands.
• One person at VaultaPay can decide and sign off a stage within five working days.

Not included

Cards. ONE.io's API does not issue payment cards. The card product does not carry across and nothing here replaces it.

Crypto trading. The Talos RFQ integration runs over WebSocket with its own signing, quote lifecycle and execution handling. It is a different order of work from the REST integration and is quoted separately if and when you want it.

Compliance tooling. AML monitoring, transaction screening, case management and risk scoring sit with ONE.io. We display the states their API returns; we do not build a compliance system.

Identity verification storage. No KYC documents or verification data are held in your Omniom instance, by design.

Data migration. No records are migrated from Swiss Fiat.

Design. This builds on the Omniom design system. A bespoke identity, including anything modelled on the Coinsfly look, is a separate exercise and is quoted once you have decided.

Mobile app. A wrapped mobile version of the client portal is phase two.

Third-party fees. ONE.io, Sumsub, domains, certificates and any provider charges are contracted and paid by VaultaPay directly.

Regulatory scope. Omniom is a software platform. We are not a regulated financial services firm, we hold no client funds and we make no AML, sanctions or verification decisions. Payment services are provided by One.io UK Limited, an Authorised Payment Institution regulated by the FCA (FRN 913478); crypto asset services by Oneio International Limited, which is not FCA regulated. VaultaPay remains responsible for its own licensing and compliance obligations.

Terms and next step

Payment. Each stage is invoiced at its start and work begins on cleared funds. The annual licence is invoiced before the instance is provisioned. We do not offer credit terms, and equally we are never working ahead of your money nor you ahead of ours.

Validity. This quotation is valid for 30 days from the date above.

Ownership. Your data is yours, exportable in full at any time, and remains so whatever happens to the commercial relationship.

To proceed

The only decision in front of you today is stage 0. It is £1,500, takes about two weeks, and ends with an agreed screen-by-screen specification, the five questions answered, and a confirmed price for the rest. If those answers turn out to make this harder than it looks, you will have found out for £1,500 rather than for £12,000.

To start, we need:

• Confirmation to proceed with stage 0
• ONE.io sandbox access, the partner key and an introduction to their integration team
• The five questions put to ONE.io, so their answers arrive inside the two weeks rather than after them
• A view of the verified client area, so we can see what an onboarded client sees today