Payment Initiation API

Name: Payment Initiation API API
Brand: Payment Initiation API
Availability: InStock

✓ Official Vendor SpecPaymentsPayment Processingoauth241 EndpointsREST

For Agents

Initiate UK account-to-account payments through PSD2-compliant PISP flows, including domestic transfers, scheduled payments, standing orders, and international payments with consent and status tracking.

Connect the Payment Initiation API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Payment Initiation API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.

Install Jentic One Beta (Self-Hosted)

Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh

Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh
jentic register       # connects your agent to your Jentic One instance

Jentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.

Capabilities

What an agent can do with Payment Initiation API API.

Create a domestic payment consent and obtain customer authorisation via redirect SCA

Submit a domestic payment for execution once the customer has authorised the consent

Schedule a future-dated domestic payment with a specific execution date

Set up a domestic standing order with frequency, first payment, and final payment dates

GET STARTED

Start building with Payment Initiation API API

Explore with Jentic

View OpenAPI Document

The UK Open Banking Payment Initiation API (PISP) lets authorised Third Party Providers create and manage account-to-account payments directly from a customer's bank account under PSD2. It covers domestic, domestic scheduled, domestic standing order, international, international scheduled, international standing order, and file payments, each with its own consent, payment, and status resources. Strong Customer Authentication is enforced via redirect or decoupled flows, and TPPs authenticate to the bank with mTLS plus OAuth 2.0 client credentials. This is the spec implemented by every CMA9 bank in the UK.

Use Cases

Patterns agents use Payment Initiation API API for, with concrete tasks.

★ Account-to-Account Checkout

Replace card payments with direct bank transfers at checkout by initiating a domestic payment consent for the order amount, redirecting the customer to their bank for SCA, and submitting the payment once authorised. The flow settles via Faster Payments in seconds and avoids card scheme fees, which suits high-value or low-margin merchants who want lower acceptance costs.

Create a domestic-payment-consent for GBP 49.99 payable to sort code 12-34-56 account 12345678, redirect the customer to authorise it, then POST /domestic-payments with the matching ConsentId and confirm settlement via GET /domestic-payments/{DomesticPaymentId}.

Subscription and Standing Orders

Replace card-on-file subscriptions with PSD2 standing orders so customers pay weekly, monthly, or quarterly amounts directly from their bank account. The /domestic-standing-order-consents and /domestic-standing-orders endpoints capture the schedule, first payment, recurring payment, and final payment fields, removing the renewal failures and reauthorisation friction associated with expired cards.

Create a domestic-standing-order-consent for GBP 19.99 monthly with first payment dated 2026-07-01 and submit the corresponding domestic-standing-order once the customer has authorised it.

International Payouts

Send cross-border payments out of UK accounts using the international-payments resource, which carries currency, exchange rate type, charge bearer, and counterparty bank fields per ISO 20022. This avoids stitching together SWIFT instructions manually and works through the same PSD2 consent framework as domestic flows.

Create an international-payment-consent for EUR 1500 from a GBP account with a fixed exchange rate, then submit the international-payment once authorised.

AI Agent Treasury Operations

Through Jentic, an AI agent can initiate and track UK bank payments without learning the OBIE specification or managing mTLS certificates and JWS signing logic itself. The agent searches for the right payment type, loads the consent and payment operations, and executes the redirect handoff for SCA. This makes Open Banking payments accessible from agent workflows that previously could only call card APIs.

Through Jentic, search for 'initiate a UK bank payment', load the POST /domestic-payment-consents operation, create a consent for GBP 250, and return the customer authorisation URL.

Key Endpoints

41 endpoints — the uk open banking payment initiation api (pisp) lets authorised third party providers create and manage account-to-account payments directly from a customer's bank account under psd2.

METHOD

PATH

DESCRIPTION

POST

/domestic-payment-consents

Create a domestic payment consent

POST

/domestic-payments

Submit a domestic payment after consent authorisation

GET

/domestic-payments/{DomesticPaymentId}

Retrieve a domestic payment and its status

POST

/domestic-scheduled-payments

Submit a future-dated domestic payment

POST

/domestic-standing-orders

Submit a domestic standing order

POST

/international-payment-consents

Create an international payment consent

POST

/international-payments

Submit an international payment after consent authorisation

POST

/file-payments

Submit a batched payment file

POST

/domestic-payment-consents

Create a domestic payment consent

POST

/domestic-payments

Submit a domestic payment after consent authorisation

GET

/domestic-payments/{DomesticPaymentId}

Retrieve a domestic payment and its status

POST

/domestic-scheduled-payments

Submit a future-dated domestic payment

POST

/domestic-standing-orders

Submit a domestic standing order

Why though Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

TPP OAuth client credentials, eIDAS-bound mTLS certificates, and JWS signing keys are stored encrypted in the Jentic MAXsystem vault. Agents receive scoped access to operations only — raw PSD2 secrets never enter the agent's context, which is critical given the FCA's TPP supervision requirements.

Intent-based discovery

Agents search by intent (e.g., 'initiate a UK domestic payment' or 'set up a monthly standing order') and Jentic returns the matching consent and payment operations with their request schemas, so the agent posts the correct InstructedAmount and CreditorAccount fields without reading the OBIE 41-endpoint spec.

Time to first call

Direct PISP integration: 6-12 weeks for TPP onboarding, mTLS, JWS signing, redirect SCA handling, and per-bank quirks. Through Jentic: under a day for the integration code once the underlying TPP authorisation is in place.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Complementary

Open Data API

Public product and directory data for the same CMA9 banks.

Choose this when the agent needs to look up bank branch, ATM, or product details rather than move money.

Alternative

Swiss NextGen Banking API-Framework

Swiss Berlin Group NextGenPSD2 implementation for cross-border PSD2 payment flows.

Choose this when the customer's account is held with a Swiss ASPSP — UK PISP only covers CMA9 and other UK ASPSPs.

Alternative

Stripe API

Card and wallet payment processing without PSD2 TPP registration.

Choose Stripe when the merchant cannot become an authorised PISP or needs international card acceptance, recurring card-on-file billing, or Apple/Google Pay alongside bank payments.

Complementary

Plaid API

Account verification and balance checks alongside payment initiation.

Choose Plaid when the agent needs to verify account ownership or check balance before initiating a payment, especially across US and EU coverage.

FAQs

Specific to using Payment Initiation API API through Jentic.

What authentication does the Payment Initiation API use?

The spec defines two OAuth 2.0 schemes: TPPOAuth2Security (client credentials grant for the TPP) and PSUOAuth2Security (authorization code grant for the customer's SCA). On top of OAuth, banks require mutual TLS for the transport layer and JWS detached signatures on POST request bodies. Through Jentic, the OAuth tokens and signing keys are isolated in the MAXsystem vault and never enter the agent's prompt context.

Can I initiate an international payment with this API?

Yes. The /international-payment-consents and /international-payments resources support cross-border payments with currency of transfer, exchange rate type (Actual, Agreed, or Indicative), charge bearer, and full counterparty bank details. Scheduled and standing-order variants exist under /international-scheduled-payments and /international-standing-orders for future-dated and recurring transfers.

What are the rate limits for the Payment Initiation API?

The OBIE spec does not mandate a single rate limit; each CMA9 bank publishes its own, typically expressed in requests-per-minute per TPP. Treat 429 responses as a signal to back off and respect the bank-specific developer portal limits. Idempotency-Key on POST is mandatory and prevents accidental duplicate payments under retry.

How do I create a domestic payment through Jentic?

Search Jentic for 'create UK domestic payment', load the POST /domestic-payment-consents operation, and execute it with the InstructedAmount, DebtorAccount, CreditorAccount, and EndToEndIdentification fields. Redirect the customer to the bank for SCA, then load POST /domestic-payments and submit the matching ConsentId — Jentic handles the mTLS and JWS signing in MAXsystem so the agent never touches the certificate.

Is the Payment Initiation API free?

The OBIE specification itself is open, but to call live PSD2 endpoints you must register as an authorised TPP (PISP) with the FCA or another EEA competent authority and obtain eIDAS certificates. The banks do not charge per call, but TPP authorisation, ongoing supervision, and certificate provisioning carry meaningful operational cost.

Can I cancel a scheduled payment before it executes?

Yes. The /domestic-scheduled-payment-consents/{ConsentId}/cancellation-authorisations and equivalent international resources let you raise a cancellation authorisation before the execution date. Once a payment has been submitted via Faster Payments it cannot be recalled through this API — settlement is real-time and irrevocable.