CUSTOMER_MANAGEMENTCustomer Management
Provision managed personal or business customers and retrieve onboarding / KYC status.
DYNAMIC PRODUCT ENTITLEMENTS
Compose the API around the partner.
Services define which Pegasus Alfa products are enabled for the client. API scopes separately define what each credential may do inside those products. Dependencies are resolved automatically.
ACCOUNTSMulti-Currency Accounts
Read linked Pegasus Alfa accounts, balances, account status and provider-safe account metadata.
CARDSCards
Read card status, form factor, last four digits, expiry and customer card controls.
PAYMENT_HISTORYPayment History
Retrieve payment history, review state, risk status and settlement state.
INTERNAL_PAYMENTSInternal Payments
Submit controlled Pegasus Alfa-to-Pegasus Alfa payment instructions.
EXTERNAL_PAYMENTSExternal Payments
Submit controlled external payment instructions over enabled rails.
GLOBAL_TRADE_METADATAGlobal Trade References
Attach trade, invoice, purchase-order and shipment references for reconciliation.
WEBHOOKSSigned Webhooks
Receive signed, retrying customer and payment events.
Partner / Client App
→Partner Backend
→Pegasus Alfa Platform API
→Accounts · Cards · Payments · Controls
INTERACTIVE SANDBOX
Test the integration model before credentials.
This browser sandbox is intentionally isolated from production and never moves funds. Toggle services to see how dynamic entitlements affect API requests, run representative calls and copy server-side request examples.
API Explorer
Platform API v1 · isolated sample environment200 Sandbox response
Security model: real Pegasus Alfa API credentials are server-to-server secrets and must never be entered into this public page, browser JavaScript or a mobile bundle. Approved partners receive credentials separately and use the same documented request structure from their backend.
INTEGRATION BASICS
Designed for embedded and white-label delivery.
Dedicated platform credentials
Each approved integration receives an isolated client identity, scopes, service entitlements, optional IP/origin restrictions and its own rate limit.
Authorization: Bearer <clientId>.<apiKey>Versioned API surface
Integrations use the Pegasus Alfa Platform API v1 surface. The assigned API host is provided with sandbox or production credentials.
/api/platform/v1Existing controls remain authoritative
API-originated payment instructions retain Pegasus Alfa onboarding, KYC, risk, limits, idempotency and controlled-review requirements.
Idempotency-Key: partner-request-001Reconciliation-ready metadata
Trade platforms can attach trade, invoice, purchase-order and shipment references when the Global Trade service is enabled.
tradeReference · invoiceReference · purchaseOrderReference · shipmentReferenceSigned events with retries
Customer and payment events can be delivered to approved HTTPS endpoints with HMAC-SHA256 signatures and retry handling.
X-Pegasus-Signature: sha256=<hmac>Partners choose; Pegasus Alfa approves
A partner may request a different service mix without changing API credentials. Sensitive capabilities become active only after Pegasus Alfa approval.
POST /api/platform/v1/services/requests