Browse the API specifications
Select a version to open the interactive API specification explorer on Backbase.io:Available API domains
The following API domains are available in the unified API specification. Each domain defines the contract that connectors must implement to expose the corresponding banking capability.Party
Party
API:
grandcentral-party-apiManages the creation, retrieval, and update of party (customer and business) records. Provides the isCustomer flag to distinguish customer parties from non-customer parties, and supports beneficiary verification operations.Implemented by: core banking connectorsParty lifecycle
Party lifecycle
API:
grandcentral-party-lifecycle-apiManages identity verification and customer onboarding workflows. Supports applicant creation, identity verification result retrieval, document download, customer screening against global watchlists (sanctions, PEPs, adverse media, AML), and Confirmation of Funds (CoF) consent management.Implemented by: KYC/KYB connectors (ComplyAdvantage, Onfido, Prove)Party reference
Party reference
API:
grandcentral-party-reference-apiProvides event-based support for receiving updates on party fields such as email address, phone number, and postal address. Enables inbound party reference connectors to keep party data synchronized.Implemented by: core banking connectors (inbound)Payment order
Payment order
API:
grandcentral-payment-order-apiManages the full payment lifecycle: initiation, validation, status retrieval, fee calculation, bank details lookup, standing orders, and scheduled payments. The v2 specification (from 2026.04) aligns with ISO 20022 standards, adding support for remittance information, regulatory reporting, FX contract tracking, and structured address formats.Implemented by: payments connectors (OBPM, Alacriti, SurePay)Batch payment
Batch payment
API:
grandcentral-batch-payment-apiSupports creating and cancelling batches of payments in a single operation. Designed for high-volume use cases such as payroll, vendor transfers, and reimbursements.Implemented by: batch payments connectors (OBPM Batch, Alacriti Batch)Servicing consent
Servicing consent
API:
grandcentral-servicing-consent-apiManages Open Banking consent flows for Account Information Services (AIS), Payment Initiation Services (PIS), and Confirmation of Funds (CoF). Supports Berlin Group and Open Banking scheme filters for consent deletion.Implemented by: Open Banking connectors (Salt Edge)Fraud detection
Fraud detection
API:
grandcentral-fraud-detection-apiEvaluates fraud risk during account opening and transaction processing. Returns risk scores, riskIndicators detailing matched fraud signals, and a decisionFlag providing the vendor-recommended action (Allow, Block, Challenge, or Quarantine).Implemented by: fraud detection connectors (Feedzai, BioCatch)Location data management
Location data management
API:
grandcentral-location-data-management-apiProvides address autocomplete and address metadata retrieval for US and international addresses. Banks use the metadata to apply their own validation logic for address input acceptance.Implemented by: address verification connectors (Smarty)Deposit
Deposit
API:
grandcentral-deposit-eventProvides event-based deposit account data aligned with the grandcentral-deposit-api specification. Enables downstream systems to receive deposit account updates through event streams.Implemented by: core banking connectorsRelated topics
- Architecture and unified APIs — how the unified API layer works and its relationship to BIAN standards
- Get started with connectors — how to build a connector that implements a unified API