Build your submission
Complete each step, attach your evidence, and download a ZIP to attach to your LFI 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 LFI.
Scope & Single Instant Payment ticket
Choose the standards version and segments, state the payment limit you enforce for Delegated SCA, and give the JIRA ticket for your completed Single Instant Payment certification — Delegated SCA builds on it, so that certification must be in place first.
The maximum amount a single Delegated SCA payment can take through Open Finance on your LFI. The TPP manages the consent controls, but your own institutional limit still applies — and it MUST NOT be more restrictive than your other digital channels.
No control parameters for Delegated SCA
A Delegated SCA consent carries IsDelegatedAuthentication: true with an empty ConsentSchedule — the TPP defines and manages the payment controls, so there are no ControlParameters scenarios to evidence. You evidence Creditor / Risk handling and the three beneficiary models instead.
See the Delegated SCA API guide ↗ for the delegated-authentication model.
Evidence
Attach the evidence below. All evidence must come from the AlTareq Model Bank sandbox.
Testing Tool output optional
Optionally attach the Testing Tool HTML report for your Ozone Connect payment endpoints. This is not required for Delegated SCA — the certification is consent-focused — but you may include it as supporting evidence.
Creditor validation & Risk handling
The Creditor account arrives inside the encrypted PersonalIdentifiableInformation, so evidence decrypting it and validating the creditor. The Risk object (AERisk) is cleartext — evidence that it is received and used in your fraud/screening. Re-captured for Delegated SCA because your validation may differ slightly under delegated authentication.
Beneficiary models
A Delegated SCA consent is authorised against a beneficiary model fixed by the shape of the decrypted PII's Initiation.Creditor. Evidence one authorised pre-production consent for each model — Single (one creditor), Multiple (2–10 fixed creditors) and Open (no creditor fixed at consent; the creditor is supplied at POST /payments). You must advertise support for the Multiple and Open models on your Trust Framework authorisation-server entry. See the Creditor PII page ↗ for the model definitions.
Single Beneficiary
The consent fixes exactly one creditor entry in Initiation.Creditor. Every payment under the consent must be to that beneficiary.
Reference — decrypted PersonalIdentifiableInformation
{
"Initiation": {
"DebtorAccount": {
"SchemeName": "IBAN",
"Identification": "AE460090000000123456789"
},
"Creditor": [
{
"Creditor": {
"Name": "Ivan England"
},
"CreditorAccount": {
"SchemeName": "IBAN",
"Identification": "AE070331234567890123456",
"Name": {
"en": "Ivan David England"
}
}
}
]
}
}Multiple Beneficiaries
The consent fixes 2–10 creditor entries in Initiation.Creditor. Every payment must exactly match one of them.
Advertise via ApiMetadata.DelegatedSCA.MultipleBeneficiariesSupported.
Reference — decrypted PersonalIdentifiableInformation
{
"Initiation": {
"DebtorAccount": {
"SchemeName": "IBAN",
"Identification": "AE460090000000123456789"
},
"Creditor": [
{
"Creditor": {
"Name": "Ivan England"
},
"CreditorAccount": {
"SchemeName": "IBAN",
"Identification": "AE070331234567890123456",
"Name": {
"en": "Ivan David England"
}
}
},
{
"Creditor": {
"Name": "Al Noor Trading LLC"
},
"CreditorAccount": {
"SchemeName": "IBAN",
"Identification": "AE320260001234567890123",
"Name": {
"en": "Al Noor Trading LLC"
}
}
},
{
"Creditor": {
"Name": "Emirates Telecommunications Group"
},
"CreditorAccount": {
"SchemeName": "IBAN",
"Identification": "AE980350000009876543210",
"Name": {
"en": "Emirates Telecommunications Group"
}
}
}
]
}
}Open Beneficiaries
The consent omits Initiation.Creditor entirely. No creditor is fixed at consent; the TPP supplies it on each POST /payments, where your Ozone Connect endpoint validates it.
Advertise via ApiMetadata.DelegatedSCA.OpenBeneficiariesSupported.
Reference — decrypted PersonalIdentifiableInformation
{
"Initiation": {
"DebtorAccount": {
"SchemeName": "IBAN",
"Identification": "AE460090000000123456789"
}
}
}Review & generate
Review the summary below, add any comments, then download your submission. The ZIP contains a summary.html and every screenshot — attach it to your LFI Functional Certification Evidence Service Desk ticket.
- Organisation
- —
- Submitted by
- —
- Version
- V2.1
- Payment type
- DelegatedSCA
- Segments
- —
- Payment limit
- —
- SIP JIRA ticket
- —