Customer authorisation
The customer gives the authorisation required for supported wallet actions.
Platform foundations
Customer authority. Clearly explained.
The intended wallet model separates customer authority over assets from the bank’s decisions about access to its product experience.
Product information describes the intended offering. Scope, availability and rollout are agreed with each bank, subject to the applicable product, provider and approval requirements.
Product access and asset authority are different.
Bank product decisions
The bank controls eligibility and the products and activities offered through its service.
A model to evaluate
Signing, recovery and operational requirements must fit the bank’s accepted operating model.
Agree the control model before integration.
The proposed customer-controlled model must be assessed against the bank’s legal and operating requirements. Restricting access to a service is not the same as freezing customer-held assets.
The website does not claim simultaneous unrestricted customer control and guaranteed unilateral bank recovery or confiscation. Detailed arrangements belong in the bank evaluation.
Operating model
Each party has a clear role.
Your bank
Owns the customer relationship, eligibility, product and asset selection, bank controls, fiat decisions and final integration.
Your customer
Reviews the intended action and gives the authorisation required for that product or bounded future instruction.
Mammoth
Provides reusable interfaces and integrations, transaction validation, monitoring, reconciliation and product records.
Execution providers
Execute the relevant action and apply their own contract, service, issuer or protocol rules.
From intent to outcome
A visible state at every step.
Choose
The customer selects an eligible product or action.
Check
The bank checks the offering, customer eligibility, limits and applicable funds.
Prepare
Mammoth validates the proposed route, permissions and transaction.
Authorise
The customer signs the action or grants the required bounded authority.
Execute
The relevant provider processes the authorised action.
Reconcile
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
Questions, answered.
The practical details behind the intended offering.
Does limiting app access freeze the customer’s wallet?
No. Service access and customer-held asset authority are different. The applicable control model must be evaluated and agreed with the bank.
Are recovery details available in the public guide?
The public guide explains the model at a high level. Detailed signing, recovery and operating arrangements are reviewed with approved bank teams.