Intraday repo

Turn tokenized securities into intraday liquidity

Run repo on Prividium with institutional controls and private execution.

Build less from scratch

Start with the repo application and controls, then connect your systems.

Control access and activity

Decide who can participate, what they can do and what they can see.

Connect your counterparties

Run repo across Prividium environments or between organizations in one deployment.

Keep operations informed

Track transactions and send activity notifications to your systems.

Architecture

How the application fits into your institution

The repo application is built using Prividium Commander. Prividium Ledger provides private execution. Connections to identity, signing or custody providers and internal systems are configured for the implementation.

Repo across separate Prividium environments

The borrower and lender participate through their own Prividium environments. Cross-Prividium interoperability connects the opening and closing exchanges, while each institution connects its own systems and providers to its environment.

Borrower institution

Treasury and securities systems

  • Identity provider
  • Signing or custody provider
  • Cash systems
  • Securities systems

Connects to Commander

Instructions and results

Borrower Prividium environment

Intraday Repo applicationTerms · Positions · Maturity · Trade history
Status and events

Prividium CommanderOrchestration layer

Workflow orchestration
Core permissionsOrganizations · Users · Authorized actions
Tokenization EngineControlled token operations
Policy EngineTransaction conditions · Required approvals
Logging and audit
Data Engine
Transaction StatusLookup and investigation
WebhooksSupported event notifications
Execution results
Prividium LedgerPrivate execution · Repo contracts and tokenized assets
Opening and closing exchangesCross-Prividium interoperability

Lender institution

Treasury and securities systems

  • Identity provider
  • Signing or custody provider
  • Cash systems
  • Securities systems

Connects to Commander

Instructions and results

Lender Prividium environment

Intraday Repo applicationTerms · Positions · Maturity · Trade history
Status and events

Prividium CommanderOrchestration layer

Workflow orchestration
Core permissionsOrganizations · Users · Authorized actions
Tokenization EngineControlled token operations
Policy EngineTransaction conditions · Required approvals
Logging and audit
Data Engine
Transaction StatusLookup and investigation
WebhooksSupported event notifications
Execution results
Prividium LedgerPrivate execution · Repo contracts and tokenized assets

Architecture view. The application carries the repo workflow. Commander connects governed operations with execution results and notifications. Cross-Prividium interoperability connects the participating environments. Dotted lines show client-specific system and provider connections.

Explore Commander

Repo within one Prividium deployment

Multiple organizations can use the application within a single Prividium environment. Borrower and lender participate as separate organizations, with their users, permissions and system connections configured for the deployment.

Single Prividium deployment · multiple organizations

Organization · Borrower
Organization · Lender
Instructions, results and notifications
Instructions, results and notifications
Intraday Repo applicationAgreed terms · Opening exchange · Maturity · Closing exchange
Application interfacePositions · Transaction status · Trade history

CommanderOrchestration layer

Workflow orchestration
Core permissionsOrganizations · Users · Authorized actions
Policy EngineTransaction conditions · Required approvals
Tokenization EngineControlled token operations
Logging and audit
Data Engine
Transaction StatusLookup and investigation
WebhooksSupported event notifications
Execution results to Transaction Status

Prividium LedgerPrivate execution

Repo contracts
Participating organizations’ tokenized cash and securities
  • Identity provider
  • Signing or custody provider
  • Cash systems
  • Securities systems

Connect to Commander

Architecture view. Both organizations use the repo application within one deployment. Their cash and collateral exchanges execute within that Prividium environment. Each organization sees only its own data. The Prividium operator can see all data in the deployment.

Modules

Built with Prividium Commander

Core permissions

Control who can participate and which actions they can take.

Tokenization Engine

Manage supported operations on tokenized cash and securities.

Data Engine

Investigate transactions with Transaction Status, notify connected systems with Webhooks, and review activity with audit logs.

Frequently asked questions

Can we keep our existing systems and providers?

The implementation can connect the application to existing treasury and securities systems, enterprise identity and chosen signing or custody providers. Specific connections and the cash and securities settlement paths are defined for each client.

Where does transaction data reside?

In a private-chain deployment, data is held within the infrastructure operating Prividium. Separate deployments have their own operating environments. In a shared deployment, each organization sees only its own data. The Prividium operator can see all data in that deployment.

Explore privacy and security
Which cash and collateral assets can we use?

Asset eligibility, issuance or representation, custody and settlement arrangements are established for the implementation. We assess the selected cash and securities together, including how each opening and closing exchange will execute.

Discuss your intraday repo implementation

See the working demo with our team and explore how it fits your institution’s funding or lending activity. Bring the assets, counterparties and systems involved. We will map the deployment, controls and connections, then identify the integration work needed for your environment.

Request a walkthrough