Platform Handbook

1. General

Welcome to the Goverion Platform

The Goverion Platform is the unified infrastructure through which clients access settlement, payment, compliance and financial management services. This handbook provides operational guidance for using the platform effectively and in accordance with its design.

Webhook configuration

Webhooks allow the platform to send real-time notifications to your systems when specific events occur. To configure a webhook, you specify the endpoint URL and select the event types you want to receive. The platform will send a POST request to that URL whenever a matching event is triggered. Ensure your endpoint is accessible and returns a 200 response to confirm receipt. Failed deliveries will be retried according to the platform's retry schedule.

Default currency

Your default currency is set during onboarding and determines the base denomination used for balance display and reporting. It can be updated within account settings. Changing the default currency affects how balances are presented but does not alter underlying transaction records or settlement denominations.

API keys

API keys are issued per workspace and are used to authenticate programmatic access to the platform. Keys should be treated as credentials and must not be shared or committed to version control. If a key is compromised, it should be revoked immediately within the platform and a new key issued. Keys can be scoped to specific permission levels depending on the access required.

Multiple workspaces

The platform supports multiple workspaces, allowing businesses to separate operational environments, entities or use cases within a single account structure. Each workspace has its own configuration, permissions and transaction history. Access to each workspace is managed independently and subject to the relevant onboarding requirements.

Travel rule

The Travel Rule requires that identifying information about the originator and beneficiary of a transaction is collected and transmitted alongside transfers above defined thresholds. Goverion applies Travel Rule requirements in accordance with the regulatory frameworks applicable to each corridor. Clients may be required to provide or verify counterparty information before a transaction can proceed. Where the Travel Rule applies, compliance is mandatory and cannot be bypassed.

Goverion products

The platform supports multiple currencies, both fiat and digital assets. In test and sandbox environments, transactions are simulated and do not involve real funds. Production environments use live balances and real settlement. Clients should verify the environment in use before initiating transactions. For questions about product functionality, contact the support team through the designated channel.

About Goverion

Goverion operates as an infrastructure and settlement provider, not as a regulated financial institution. Client funds are held by licensed partner institutions, not by Goverion directly. Complaints can be submitted through the designated complaints process available within the platform. Goverion has a whistleblowing policy for reporting concerns about conduct or compliance. Where APP (authorised push payment) fraud is suspected, clients should contact Goverion immediately. Support is available during published business hours.

Reporting

The platform provides comprehensive reporting tools including wallet balance exports, CSV transaction reports and searchable transaction history with running balance views. Reports can be generated for defined date ranges and filtered by account, currency or transaction type. All transaction records are immutable and available for audit purposes.

Risk

The use of digital assets involves exposure to market, operational and regulatory risks. Prices can be volatile and the regulatory environment continues to evolve. Clients should assess their own risk tolerance before using digital asset functionality and ensure they understand the risks associated with each product they access.

Team member management

Additional users can be invited to the platform and assigned roles that define their access permissions. Role-based access controls determine which actions each team member can perform. Permissions should be reviewed regularly and updated when responsibilities change. Authorised representatives are responsible for managing team access within their account.

End-users

An end-user is an individual or entity that interacts with a service built on Goverion infrastructure through a partner platform. In this model, the end-user relationship is held by the partner, and Goverion provides the underlying operational infrastructure. Gas fees apply to blockchain transactions and are passed through at cost. Crypto payment functionality is available where enabled within the account configuration.

2. Platform overview

Unified financial framework

Goverion provides a unified financial framework that connects enterprise, financial networks and blockchain infrastructure. The platform enables business operations, payments, financial records and dispute resolution to function in real time across borders and jurisdictions.

Execution layer

The Execution Layer is the operational interface through which transaction instructions are received, validated and processed. It handles routing logic, currency conversion and the coordination of regulated service components.

Payment layer

The Payment Layer manages the movement of fiat funds through regulated payment schemes and banking partner infrastructure. It supports domestic and international transfers, including SEPA, Faster Payments and SWIFT where applicable.

Settlement layer (GBN)

The Goverion Blockchain Network (GBN) provides the settlement layer for the platform. It delivers deterministic, immutable finality for transactions processed through the infrastructure. The GBN records settlement events and provides a verifiable audit trail that persists independently of the payment layer.

Network validation layer

The Network Validation Layer ensures that transactions submitted to the GBN meet the required protocol standards before they are confirmed. Validation occurs prior to settlement and provides an additional layer of integrity checking.

Goverion products

The platform's four core products — Execute, Global Pay, Plug-In Pay and Treasury/Wallet — are integrated with the GBN and operate across the execution, payment and settlement layers. Each product is designed to address a specific operational use case while sharing the same compliance and audit infrastructure.

Compliance and audit infrastructure

Compliance controls are embedded at the execution layer and applied to every transaction. These include AML screening, sanctions checking, transaction monitoring and audit logging. The infrastructure is designed to satisfy regulatory requirements across the jurisdictions in which the platform operates.

Plug-In Pay infrastructure

Plug-In Pay allows third-party platforms and merchants to integrate payment acceptance and processing capabilities into their own products via a defined API. The infrastructure supports both fiat and digital asset payment flows, with compliance controls applied at the point of integration.

PSP integration

Payment service providers can integrate with Goverion infrastructure to extend their settlement and compliance capabilities. Integration is achieved via REST API and supports the full transaction lifecycle from authorisation through to final settlement.

3. Security

Counterparty exposure management

Goverion manages counterparty exposure through controls applied at the transaction and account level. These include transaction limits, monitoring thresholds and partner-based safeguarding arrangements. Exposure is assessed continuously and controls are adjusted in response to changes in activity or risk profile.

IT infrastructure safeguards

The platform is hosted on resilient, enterprise-grade infrastructure with multiple layers of access control, encryption and monitoring. Security controls are applied across all system components and reviewed regularly. Penetration testing and vulnerability assessments are conducted on a scheduled basis.

Responsible disclosure

Goverion operates a responsible disclosure policy for reporting security vulnerabilities. If you identify a potential security issue, you should report it through the designated channel rather than disclosing it publicly. Goverion will investigate and respond in accordance with the policy.

4-eye approval flows

Certain high-value or sensitive transactions require approval from more than one authorised user before they can be executed. This four-eye control is designed to reduce the risk of unauthorised or erroneous transactions. The approval requirement is configurable and applied based on transaction type, value and account settings.

ISO 27001 alignment

Goverion's information security management practices are aligned with the ISO 27001 framework. This alignment covers risk assessment, access management, incident response and continuous improvement processes.

SOC 2 Type II alignment

Goverion's operational controls are developed in alignment with SOC 2 Type II principles covering security, availability, processing integrity, confidentiality and privacy. These principles inform the design of controls across the platform infrastructure.

Custody

Fiat funds are held in segregated safeguarded accounts with licensed partner institutions. Goverion does not custody client fiat funds directly. Digital assets are held in segregated wallets with access controls designed to prevent unauthorised access. In the event of an airdrop or unsolicited asset receipt, Goverion will determine the appropriate course of action in accordance with its custody policy.

Insurance

Goverion maintains insurance coverage relevant to its operational activities. Specific coverage details are available on request. Insurance does not replace the obligation to implement appropriate security and operational controls.

Two-factor authentication (2FA)

2FA is required for access to the platform and is applied at login and for certain sensitive actions. Supported methods include authenticator apps and hardware tokens. To enable 2FA, navigate to security settings within your account. If access is lost, the reset process requires identity verification through the support team.

Password security

Passwords must meet the complexity requirements set out in the platform's security policy. Passwords should not be reused across services and should be stored using a password manager. If you suspect your credentials have been compromised, you should change your password immediately and contact support.

4. Legal & regulatory

Goverion terms and documents

The Goverion Terms and Conditions are the primary contractual framework governing access to and use of the platform. They set out the legal basis on which Goverion makes its infrastructure available, define the service perimeter, allocate responsibilities between Goverion and licensed partner institutions, and establish the rights and obligations of each client. Goverion does not act as a bank and does not custody client fiat funds. Fiat funds are held and processed by regulated Electronic Money Institutions, payment institutions and banking partners. Any breach of the Terms and Conditions may lead to the restriction of specific services, suspension of account activity or termination of platform access.

Goverion Acceptable Use Policy (Financial Crime)

The Goverion Acceptable Use Policy (Financial Crime) explains the categories of activity that are prohibited on the platform and the controls Goverion applies to prevent misuse of its infrastructure for unlawful purposes. The policy covers activity linked to money laundering, terrorist financing, fraud, sanctions evasion, market abuse, deceptive practices and the use of the platform by prohibited businesses or entities operating outside acceptable risk appetite. Clients must ensure that the source and destination of funds are lawful and that activity conducted through the platform is consistent with the business profile disclosed at onboarding. The platform applies monitoring at the transaction layer. Where activity falls outside expected parameters, a transaction may be delayed, placed into review or blocked.

Goverion Acceptable Use Policy (Product and API)

The Goverion Acceptable Use Policy (Product and API) sets out the operational boundaries for use of the platform, including how the Merchant Portal, APIs, webhooks and related services may be accessed and used. The purpose of the policy is to preserve system integrity, security and service availability. Behaviour that attempts to bypass authentication, manipulate workflows, create instability or misuse infrastructure for unintended purposes is not permitted. Where APIs are used, credentials are issued on a client-specific basis and access is controlled by role, environment and permission scope.

Privacy Policy

The Privacy Policy explains how Goverion collects, uses, stores, shares and protects personal data in the course of providing services. This includes data provided during onboarding, data generated through transactions and data processed to satisfy legal and regulatory obligations. The policy is designed to align with data protection requirements applicable in the jurisdictions in which Goverion and its partners operate, including UK and EU privacy frameworks where relevant.

Data Protection Addendum

The Data Protection Addendum governs the allocation of data protection responsibilities between Goverion and its business clients where personal data is processed in connection with the services. It explains when Goverion acts as a processor, when it may act as a controller, and what security and operational standards apply to that processing.

GLBA Privacy Notice

The GLBA Privacy Notice applies to US-relevant services where financial information is handled in a way that falls within US privacy and safeguarding requirements. It explains what types of financial information may be collected, how that information may be shared and the controls that apply to protect it.

US and Malta partner platform customers

For clients accessing services through a US partner platform, the end-user relationship is held primarily by the partner platform, while Goverion provides the operational infrastructure supporting execution, routing and settlement. For Malta-regulated services, e-money account terms apply, covering the legal nature of the account, how balances are held and what rights of redemption exist. Specific terms apply to stablecoin payout functionality and embedded wallet experiences within each jurisdiction.

Service partners

Where Goverion relies on third-party digital asset or token infrastructure providers (such as Paxos), the applicable partner terms, privacy notices and disclosures are made available to clients using those components. Where banking infrastructure is provided by Lead Bank or an equivalent partner, the applicable bank terms govern the regulated banking relationship. Cross River Bank privacy policies apply where that institution is part of the service chain.

General legal documents

Additional documents available within the platform include the IRS Form 1099-DA guidance (for US tax reporting obligations), white papers providing technical and architectural information about the Goverion Blockchain Network, the Service Level Agreement defining platform availability and support standards, the Test Agreement Terms and Conditions governing sandbox access, and the Website Terms of Use and Cookies Policy.

Accessing services in the UK

Before a UK-relevant client can access services, Goverion must take that client through a mandatory onboarding sequence designed to reflect UK financial promotions and related compliance requirements. This includes a standard risk warning (which must be acknowledged before onboarding can continue), a 24-hour cooling-off period for first-time access where applicable, client self-categorisation and an appropriateness assessment. Self-categorisation must be renewed periodically. The appropriateness assessment is a questionnaire-based process used to assess whether the client has sufficient understanding of the service and its risks — completion is mandatory where it applies.

Electronic Money Institution (EMI)

An EMI licence permits an authorised institution to issue electronic money and provide certain payment services under the supervision of the relevant regulator. In Goverion's model, EMI-regulated partners support the fiat account and payment side of the service. An EMI-supported account gives the client access to regulated fiat capabilities such as receiving funds, holding balances and making payments through supported payment schemes. E-money funds are protected through safeguarding arrangements required of the licensed EMI. The available currencies and payment schemes depend on the EMI partner, the jurisdiction and the account structure.

Goverion licences

Goverion operates through a multi-entity and partner-supported model. Not every component of the service is delivered by a single legal entity. Instead, the regulated components are delivered by the entity or partner authorised to provide them in the relevant jurisdiction. Fiat accounts and e-money functionality sit with licensed EMI or banking partners, while digital asset service elements may sit with authorised virtual asset or digital asset service providers where relevant. The client is informed during onboarding which entity or partner framework applies to the services they are using.

Law enforcement enquiries

Law enforcement requests relating to digital asset or virtual asset services must be submitted through the appropriate legal and international cooperation channels. Informal requests are not actioned. Requests must be addressed to the correct legal entity and must comply with the legal gateways required in the relevant jurisdiction. Where the enquiry relates to fiat accounts, e-money services or payment services, the request must be directed to the relevant EMI or banking entity responsible for that part of the service.

Request for information (RFI)

An RFI is a formal Request for Information issued when a transaction or account activity requires clarification before it can be completed or released. It is part of Goverion's compliance and risk-management process. Goverion issues RFIs where the available information is insufficient to satisfy its regulatory or risk requirements — this may happen because a transaction appears unusual, because supporting context is missing or because the platform is required to verify specific aspects of the activity. Clients are expected to respond promptly; delay may delay the release of funds. Responses should be submitted through the designated Case Management Portal with complete and clearly labelled supporting documents.

Risks

The Goverion service model involves exposure to regulatory, operational, settlement and digital asset-related risks. These risks arise from the nature of cross-border transactions, the use of digital asset infrastructure, reliance on regulated partners and changing rules across jurisdictions. Goverion mitigates risk through structural controls including real-time transaction monitoring, partner-based safeguarding of fiat funds, role-based permissions, case management processes, deterministic settlement through the GBN and a clear separation between infrastructure and regulated custody functions. No infrastructure eliminates risk entirely, even where controls are strong.

5. Receive

Depositing to your Goverion wallet

To deposit USD or other fiat currencies into your Goverion wallet, initiate a bank transfer using the virtual account details assigned to you within the Goverion Portal. These details include the account number or IBAN, routing information and a unique payment reference. The reference is required for the system to correctly identify and allocate incoming funds. Once received by the regulated financial institution supporting your virtual account, Goverion performs reconciliation by matching the incoming transfer against the reference provided. Where the reference is correct and matches your account, the transaction is allocated accordingly. Funds become available only after reconciliation, compliance checks and settlement are complete.

First-time top-up

When funding your Goverion account for the first time, the process follows the same structure as a standard deposit but with additional verification requirements. Goverion may verify the origin of funds and confirm that the sending account is associated with your business entity as declared during onboarding. This may extend the processing time of the first transaction. Once the initial deposit has been successfully received, reconciled and cleared, your account is enabled for ongoing use.

Fiat currency deposit timing

Transfers made using instant or near-instant payment schemes may be received by the partner institution within minutes. Standard domestic or international transfers may take longer due to intermediary bank processing and settlement cycles. Receipt of funds by the banking partner does not immediately make them available in your Goverion wallet — the payment must first be reconciled and pass all required monitoring and compliance checks before it is reflected in your wallet balance.

Channels

Channels are a method of organising incoming payments within the Goverion platform. They act as defined receiving pathways that allow payments to be grouped, identified and attributed based on their origin or purpose. Each channel can be associated with a contact or a specific business flow, enabling automatic categorisation of transactions. Creating a channel allows you to define a structured route through which payments are received and optionally assign a contact at the point of creation. Once a channel is created and linked to a contact, any payments received through that channel are automatically associated with that contact, removing the need for manual reconciliation. Channels can be updated as your operational requirements change.

Stablecoin payments

Stablecoins supported by Goverion are designed to maintain a one-to-one relationship with the US dollar. When such assets are received, they are treated as equivalent to USD for the purpose of reconciliation and reporting. The platform records the exact amount received on-chain and processes it accordingly. When a payment request is created, an expected amount is defined. If the amount received is lower than expected, the payment is recorded as partially fulfilled and the shortfall remains outstanding. If the amount received exceeds the expected value, the full amount is credited and any excess remains in the wallet balance. A payment link can be generated within the platform and shared with a contact to facilitate crypto pay-in. Crypto payments can also be received directly through a channel linked to a wallet address. Cryptocurrency transactions are generally irreversible once confirmed on the blockchain — recovery of incorrectly sent funds cannot be guaranteed.

6. Send

Creating payouts

When creating a payout from your Goverion Virtual Account, beneficiary details must be entered accurately before the payment can be submitted. Where supported by the payment scheme, Verification of Payee is applied to confirm that the beneficiary name corresponds to the receiving account. If a mismatch is identified, the discrepancy is shown and you must either correct the details or confirm the payment, depending on how verification is enforced. Verification is completed before the payment is submitted.

Fiat payouts

To send a fiat payout, select or create a beneficiary account, enter the payment amount and confirm the transaction. Once the payment is authorised, the amount is deducted from your available balance and the payment is submitted to the selected payment scheme. The instruction has been passed to the banking network and cannot be cancelled through the platform. The transaction is completed once it has been accepted and credited by the beneficiary's bank.

Fiat mass payouts

Fiat mass payouts allow multiple payments to be created and submitted in a single operation. Each payment within the batch includes its own beneficiary details and amount. When a batch is submitted, each payment is validated and processed individually. If any payment within the batch fails or is rejected, it is returned separately and does not affect the processing of other payments within the batch.

Fiat payin refund

A fiat pay-in refund allows you to return funds that were previously received into your Goverion Virtual Account — typically used where a payment has been received in error, requires reversal or needs to be returned to the sender. To initiate a refund, you select the original incoming transaction and create a corresponding outbound payment. Where possible, the refund is directed back to the originating account.

Withdrawals

Before withdrawing funds, you must add a beneficiary bank account to your Goverion profile. Once added and approved, it becomes available for selection when initiating withdrawals or payouts. To withdraw fiat currency, create a payout to a registered beneficiary account, select the account, enter the withdrawal amount and confirm the transaction. The withdrawal is considered complete once the receiving institution has accepted and credited the funds.

B2B payments

The "Pay" function becomes available once your account is fully configured and approved for payments, including completion of onboarding, verification checks and any required permissions. After a B2B payment is initiated, the transaction is submitted to the selected payment scheme and enters processing. The transaction status is updated as it progresses. If you are unable to make B2B payments, it may be due to incomplete onboarding, missing verification, insufficient balance or restrictions applied to your account.

Payment schemes

Goverion supports multiple payment schemes depending on the currency and jurisdiction of your account, including SEPA, Faster Payments and SWIFT. SEPA Instant and Faster Payments support near real-time transfers but may impose lower transaction limits. SEPA Credit allows higher transaction values but is processed over standard banking timelines. The schemes available to you are determined by your account setup and the services enabled during onboarding.

Stablecoin payouts

When sending stablecoin payments, network fees are applied to process the transaction on the blockchain. You may choose to include these fees within the payment amount or pass them on to the recipient. Auto-refund functionality allows certain transactions to be returned automatically to the originating address where a transaction cannot be processed or does not meet defined conditions. To send a crypto payout, enter the destination wallet address, select the asset and define the amount to be transferred. Proof of wallet ownership is required to confirm that you control the destination address used for crypto payouts.

7. Store

Payment tracking and proof of payment

All payments processed through Goverion are recorded at the point of execution and updated as they move through the relevant processing and settlement layers. Each transaction contains a unique reference, timestamps, counterparty details and status indicators reflecting its progression. A payment marked as executed confirms that the instruction has been accepted and processed within the payment infrastructure. A payment marked as completed reflects that the receiving institution or network has accepted the funds and no further reversal is possible within the standard flow. All transaction records are immutable once executed and remain available for audit, reconciliation and reporting.

Proof of payment

Proof of Payment confirms that a payment instruction has been executed and submitted to the relevant network. It includes transaction identifiers, beneficiary details and execution timestamps. It does not, in isolation, confirm receipt by the beneficiary, as this depends on the receiving institution or blockchain confirmation. You can download the Proof of Payment from the transaction details within your Goverion dashboard.

Cut-off times

Cut-Off Times determine the processing window for fiat payment instructions. These are defined by the underlying banking schemes and vary by currency, jurisdiction and payment method. A payment submitted before the applicable Cut-Off Time is processed within the same operational cycle. A payment submitted after this point enters the next available processing cycle. Cut-Off Times apply only to fiat payment execution — settlement timing is dependent on the receiving institution or, in the case of digital asset transactions, on network confirmation.

Goverion Embedded Wallet

The Goverion Embedded Wallet is the operational interface through which balances are represented and managed. It reflects positions across fiat accounts held with regulated partners and digital assets recorded on blockchain networks. Fiat balances displayed within the wallet correspond to funds held in safeguarded accounts with licensed institutions — Goverion does not custody these funds. Digital asset balances are recorded against segregated wallet addresses and are controlled through secure access mechanisms. The wallet does not create settlement; it reflects the outcome of executed and settled transactions.

Virtual accounts

Customer Virtual Accounts are created to assign unique receiving details to individual counterparties or use cases. Each virtual account is mapped to your primary account structure and linked to a specific customer or transaction flow. Incoming payments received through a virtual account are automatically attributed to the assigned counterparty, removing the need for manual reconciliation. Virtual accounts can be created within the platform, each linked to your core account structure and assigned to a specific counterparty or operational purpose.

Beneficiaries and bank accounts

A beneficiary is added by submitting the required account details including name, account number and routing information. Before a beneficiary can be used, verification may be required depending on the payment scheme and compliance requirements. All beneficiary records are stored and can be reused for future transactions. A beneficiary can be deleted at any time, but deletion removes them from the available payment list and does not affect historical transactions. A bank account can be deleted only when it holds no balance and has no pending or in-flight transactions.

Onboarding and KYB

Onboarding requires submission of documentation to verify the identity, structure and activity of the business. This includes incorporation documents, ownership information and identification of relevant individuals. Additional documentation may be requested based on jurisdiction, business model and regulatory requirements. KYB (Know Your Business) is required to establish the identity and legitimacy of the business and to ensure compliance with applicable regulatory obligations. Without completion of KYB, access to core services including payments, virtual accounts and digital asset functionality cannot be enabled. If the client's structure changes or if activity on the account differs materially from the profile disclosed at onboarding, additional or refreshed KYB documentation may be required.

8. Convert

Currency conversion

Conversion rates are derived from aggregated institutional liquidity sources including exchanges and liquidity providers. These rates reflect live market conditions. When initiating a conversion, an indicative rate is first displayed. Upon request, a firm quote is provided. This quote includes the applicable spread and is valid for a defined period. Once the quote is accepted within the validity window, the rate is locked and the transaction is executed. After execution, the rate does not change. All pricing is inclusive of spread unless otherwise agreed under a specific commercial arrangement.

Convert on merchant portal

Conversions executed through the platform follow a defined sequence. You select the source asset or currency, the target currency and the amount. An indicative rate is displayed. When you proceed, a firm quote is provided for confirmation. Once confirmed, the conversion is executed immediately. The source balance is debited and the converted value is credited without delay. The updated balances are reflected in real time. The transaction is recorded and cannot be reversed once executed.

Conversion with Goverion

Conversions can be executed as standalone transactions or as part of a broader payment or treasury workflow. In operational use, incoming funds may be converted upon receipt, outgoing payments may include conversion prior to execution, and treasury balances may be converted to manage currency exposure. In all cases, conversion occurs at the point of execution using a firm quote. Once executed, the converted value becomes immediately available. Conversion does not rely on external clearing systems — it is completed within the execution layer and reflected instantly within the account.

OTC and large volume conversions

For large or price-sensitive transactions, conversions are executed through an OTC (over-the-counter) process. A request for quote (RFQ) is submitted, a firm price is provided based on current market liquidity, the quote is valid for a defined time window and execution occurs once the quote is accepted. This process ensures price certainty, reduced slippage and execution at size without market impact. OTC execution may involve direct interaction with liquidity providers. Once executed, the converted value is credited immediately and recorded within the account.

Receiving cryptocurrency into your account

To send cryptocurrency to your Goverion virtual account, use the wallet address provided within the platform for the specific asset and network. You initiate the transaction from an external wallet or exchange, entering the correct wallet address and the correct blockchain network. Once submitted, the transaction is broadcast to the network and progresses through confirmation. After the required confirmations are reached, the asset is recorded within your account and becomes available for use. If an incorrect network or unsupported asset is used, the transaction may not be recoverable.

Cryptocurrency deposit timing

A cryptocurrency deposit is reflected once it has reached the required number of confirmations on the blockchain network. Before confirmation, the transaction is not considered final. After confirmation, the balance is updated immediately. The time required depends on the network used, current network conditions and the confirmation requirements for the asset. Once confirmed, the balance is available for conversion, transfer or settlement without delay.

Fiat settlement from crypto receipt

When cryptocurrency is received, the transaction is first processed and confirmed on the underlying blockchain network. Once the confirmation threshold is reached, the digital asset is recognised within your account and becomes available for conversion. If conversion to fiat is initiated, execution occurs at the point a firm rate is accepted. The conversion is completed immediately and the resulting fiat value is recorded within your virtual account. Settlement finality is achieved once the blockchain transaction has reached the required confirmations and the conversion has been executed.