GIBP

Compliance & policy

Rule out prohibited routes before comparing price or speed.

The proposed platform would apply each institution's legal, jurisdictional and risk restrictions before evaluating payment or settlement alternatives. Institutions and their authorised providers would retain their own compliance responsibilities.

GIBP provides software, integration, policy and evidence capabilities. It does not claim that software alone discharges every legal or regulatory obligation of an institution.

Institutional verification signals

Integrate approved KYC/KYB and institutional-verification providers; apply their outputs to policy rather than claiming a universal native verification service.

Sanctions and counterparty policy

Use screening and institutional limits to remove ineligible paths before an execution plan can be selected.

Jurisdiction and asset policy

Represent corridor, asset, customer and counterparty restrictions as versioned execution constraints.

Travel Rule interoperability

Architecture can map Travel Rule / IVMS-101 information where applicable; scope depends on provider, asset, jurisdiction, contract and implementation evidence.

Audit and decision evidence

Record the policy version, inputs, rejected options and selected plan so reviewers can understand the decision.

Compiler model

Remove impermissible routes before price optimisation.

Input

Intent + entity + jurisdiction + asset + mandate + counterparty context

Policy

Versioned institution and jurisdiction rules

Output

Permitted execution graph + machine-readable rejection reasons

Optimisation

Only permitted plans are compared economically

Current regulatory position is published separately.

Live regulated activity, licence scope, asset treatment and responsibility allocation depend on the actual service, contract and jurisdiction.

Regulatory position
Ask