Payments (Service Initiation) 2 min read
The Payment Service Initiation capabilities allow customers to authorise payments at their LFI which a TPP then submits within the bounds of that authorisation. Payment types range from one-time instant payments through to long-running multi-payment consents with variable amounts, schedules, or delegated authentication.
Bank Service Initiation Provider
Access to the Payment Service Initiation APIs requires TPPs to hold the BSIP role. The API Hub validates the role on every request before proxying it to the LFI. If the consent also includes data-sharing permissions (ReadAccountsBasic, ReadAccountsDetail, ReadBalances), TPPs additionally require the BDSP role.
Who's initiating Payments
TPPs currently submitting payments across UAE Open Finance.
Browse this section
The full set of pages for the Payments (Service Initiation) API.
Single Instant Payment
A one-time payment authorised and submitted in a single flow. Suited to checkout, bill settlement, and any one-known-amount payment to a known recipient.
Variable On Demand
Variable amounts within agreed limits, triggered on demand. Suited to subscription billing, wallet top-ups, and discretionary recurring charges.
Fixed On Demand
Fixed per-payment amount, triggered on demand within the consent period.
Variable Periodic Schedule
Exactly one payment per calendar period, variable amount per payment. Suited to regular bills.
Fixed Periodic Schedule
Exactly one payment per calendar period at a fixed amount. Suited to standing payment arrangements.
Variable Defined Schedule
Payments locked to specific future dates set at consent time, variable amount per payment.
Fixed Defined Schedule
Payments locked to specific future dates at fixed amounts. Suited to instalment plans and known future obligations.
Delegated SCA
Multi-payment flows where strong customer authentication is delegated to the TPP at consent time.
Refunds
Refund initiation flow against a previously-executed payment consent.
Personal Identifiable Information
How creditor and debtor PII is presented across payment consents — encryption, payload structure, and per-LFI validation.
Multi-Authorization
Subsequent-authoriser flows for payments that require approval from more than one customer.