GIBP

Developers

Build once for the financial outcome, not for every provider.

Explore a proposed interface where your application states what needs to happen and GIBP models eligible ways to achieve it. The public sandbox uses synthetic data; its examples are not live payment APIs.

POST /v1/intents · illustrative model
{
  "deliver": { "currency": "SGD", "amount": "17283821.14" },
  "funding": { "currency": "GBP" },
  "deadline": "10:15:00+08:00",
  "constraints": {
    "finality": "required",
    "customer_crypto_exposure": false,
    "max_unsecured_exposure": "2000000"
  },
  "priority": ["certainty", "cost", "speed"]
}

Intent resources

Create and inspect financial intent, constraints and priorities.

Execution resources

Simulate plans, quotes, approvals, execution state and evidence.

Trust model

Understand policy rejection, idempotency, audit and evidence.

One canonical resource model.

SDKs and adapters should preserve route-independent semantics so provider changes do not force customer applications to understand each underlying rail.

Developer quality principles

  • • Idempotent financial state transitions.
  • • Clear access conditions and versioned contracts for every endpoint.
  • • Machine-readable policy rejection reasons.
  • • Stable execution and evidence identifiers.
  • • Synthetic examples that never imply live counterparties.

Build against the current model, not marketing promises.

API documentation describes the interface, access conditions and evidence expectations for each integration.

Explore the API model
Ask