Discover eligible assets
Show only the products and assets included in the customer’s approved offering.
Wallets, funding & investing
An intended journey for discovering, buying, holding and selling supported crypto assets in the bank’s application. Make the action, costs and current state clear to the customer.
Customer experience
Show only the products and assets included in the customer’s approved offering.
Present the asset, network, costs and relevant limits before the customer approves the action.
Distinguish preparation, processing, confirmed holdings and exceptions.
Provide the applicable receive, hold, send and sell journeys.
Your customer. Your banking app.
See how an intended investment journey could fit inside your bank’s application.
Explore the assets included in your bank’s offering.
Illustrative experience. No account, investment or transaction is created.
The bank app presents the supported offering and relevant product information.
Show usable funds, the quoted outcome, costs and any necessary network movement.
The customer approves the exact transaction under the applicable model.
Update the holding after execution and reconciliation, with clear handling of incomplete outcomes.
Every action depends on a supported asset, network, provider and deployment. Receiving an asset does not automatically mean it can be traded or used as collateral.
Native Bitcoin currently sits in the intended receive-and-send scope. Native Bitcoin trading remains deferred.
Asset values can fall. The illustrative website experience does not provide investment advice or execute trades.
Operating model
Owns the customer relationship, eligibility, product and asset selection, bank controls, fiat decisions and final integration.
Reviews the intended action and gives the authorisation required for that product or bounded future instruction.
Provides reusable interfaces and integrations, transaction validation, monitoring, reconciliation and product records.
Execute the relevant action and apply their own contract, service, issuer or protocol rules.
From intent to outcome
The customer selects an eligible product or action.
The bank checks the offering, customer eligibility, limits and applicable funds.
Mammoth validates the proposed route, permissions and transaction.
The customer signs the action or grants the required bounded authority.
The relevant provider processes the authorised action.
Actual bank, provider and network outcomes become the confirmed record.
A submitted request is not a completed transaction. Pending and exception states remain visible until the outcome is reconciled.
A little more detail
The practical details behind the intended offering.
No. Asset and network support are selected for the bank’s agreed offering and the capabilities of the applicable providers.
No. The app must distinguish pending, failed and confirmed outcomes. A holding should reflect the reconciled result.
No. This is a bank-facing information website. Its phone walkthrough is illustrative and cannot place trades.
A conversation about your bank
Explore the products, responsibilities and integration path that fit your bank.