Functional Certification · Domestic Payments

Build your submission

Complete each step, provide the Consent and Risk objects for every payment type you offer, and download a ZIP to attach to your TPP Functional Certification Evidence Service Desk ticket. New here? Read what Functional Certification involves first.

Your details

Your organisation and name are taken from your Sandbox Trust Framework session — the same sign-in used across the portal. Sign in so your submission is attributed to your organisation.

Checking your session…

Payment types

Tell us briefly why you offer domestic payments, pick the standards version, then tick every payment type you offer. For each one you will provide the Consent and Risk objects you construct, and a Postman example of a payment made against it on the Model Bank.

Use case

A sentence or two on what you use domestic payments for — for example, letting customers settle a merchant checkout, or move money between their own accounts.

Payment types you offer

Domestic Payments

0 of 8 selected

API version

Single Instant Payment A one-off payment initiated immediately after authorization — ConsentSchedule.SinglePayment with a fixed Amount.

Variable On-Demand On-demand payments of variable amounts within per-period controls and cumulative caps.

Fixed On-Demand On-demand payments of a fixed amount within per-period controls.

Variable Periodic Schedule Recurring payments of variable amounts on a period schedule, with a maximum individual amount.

Fixed Periodic Schedule Recurring payments of a fixed amount on a period schedule.

Variable Defined Schedule Pre-defined future-dated payments of variable amounts on specific dates.

Fixed Defined Schedule Pre-defined future-dated payments of a fixed amount on specific dates.

Delegated SCA IsDelegatedAuthentication: true with no ConsentSchedule — the TPP performs the SCA and manages the payment controls itself.

Optional capabilities

Beyond initiating payments, a payment consent can carry account and balance reads, and a refund-account read. Tick anything your proposition uses — you will evidence a balance read before the payment and a refund read after it.

Accounts & Balances before paymentThe payment consent carries ReadAccountsBasic/Detail and ReadBalances, so you read the debtor account and its balance before initiating the payment.

Refunds after paymentThe payment consent carries ReadRefundAccount, so you retrieve the debtor refund-account details after the payment.

Consent, Risk & evidence

For each type, edit the Consent (authorization_details) and Risk (AERisk) objects to match what you send. The objects validate against the OpenAPI schema — edits commit on blur, and anything that does not match reverts. Your evidence is produced by making a payment against a consent of each type on the sandbox AlTareq Model Bank using the Postman collection, and attaching the Postman screenshot of that payment.

You haven’t selected any payment types yet. .

Review & generate

Review the summary below, add any comments, then download your submission. The ZIP contains a summary.html, the Consent and Risk JSON for each type, and every screenshot — attach it to your TPP Functional Certification Evidence Service Desk ticket.

Organisation: —
Submitted by: —
Version: V2.1
Payment types: —
Capabilities: None

Comments (optional)

Step 1 of 4