These cookies are required for the website to function properly. They ensure security, enable basic features like page navigation, and store user session data. You cannot disable these cookies.
- Crypto Exchange Platform
- Who it's for
- Multi-provider teams
Multi-provider teams
Separate eligible counterparties and their provider-held trading accounts. Keep external account identifiers, instruction references and provider event identifiers intact. Exceptions can be reviewed by account and source rather than merged into a single undifferentiated queue.
How Crypto Exchange Platform is set up for you
Party ownership
App Administrator keeps each eligible counterparty with its organization and contact details.
Account identity
Operations Analyst keeps the external account identifier and custodian beside the account code.
Event identity
Each provider movement retains its event identifier, amount and date for exact matching.
Source correction
The team preserves an earlier event when a provider issues a later correction.
Separate eligible counterparties and their provider-held trading accounts. Keep external account identifiers, instruction references and provider event identifiers intact. Exceptions can be reviewed by account and source rather than merged into a single undifferentiated queue.
For example, two custodians may report movements of the same amount on the same day. The account and provider event identifier distinguish them. Match each movement only to an instruction linked to that account; retain a disputed provider message until its source and outcome are clear.
Pilot one provider path first. Agree which provider confirms the effect, which source supplies positions, and how a correction is recognized. Repeat the matching test before adding another provider. Run a rejected or returned review as well as an accepted one. Give the team a provider movement that differs on date or amount so the exception path is rehearsed. Record who owns the next step and how the outcome will be verified.
The first review should include the actual request owner, the independent decision maker and the person who checks the provider result. Keep their reasons and source references on the same case for the next operating cycle.
Features to start with
Roles on the team
- Auditor
- Read authorized evidence and reports in a scoped, read-only audit view. No record writes and no action execution.
- Independent Finance Reviewer
- Review eligible instruction revisions independently and reconcile operational evidence. Approve or reject through guarded actions only; no unrestricted editing of protected or executed records; a reviewer cannot approve their own submission.
- App Administrator
- Maintain organization configuration and membership. Administrative membership does not confer approval, financial or execution authority and cannot grant an independent reviewer entitlement.
- Operations Analyst
- Prepare assigned operational records and execute eligible reviewed actions. Own organization and draft scope only; accepted, posted and provider evidence is read-only; guarded workflows authorize every transition.
Set up Crypto Exchange Platform your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.