Functional Certification — Fixed Defined Schedule 3 min read
Fixed Defined Schedule is one of the six Multi-Payment types, certified after Single Instant Payment. Its certification is about the consent: you prove your LFI ingests, displays on its authorization screen, and will enforce the ControlParameters — both with every optional control set and with only the required minimum. This page explains the evidence; the portal then builds your submission.
Evidence that your consent handling is correct
A Fixed Defined Schedule consent (Type: FixedDefinedSchedule) is a long-lived multi-payment consent whose ControlParameters.ConsentSchedule.MultiPayment carries the payment schedule and its limits. Your LFI does not decide these — the TPP sets them and the customer authorizes them — but you MUST store them, show them on your authorization screen, and enforce them on every payment. Certification proves this for two consents: one with every optional control parameter populated, and one with only the required minimum. See the Fixed Defined Schedule API guide for the full model.
Required and optional controls
For Fixed Defined Schedule the ControlParameters break down as:
- Required (always present): Schedule[] (PaymentExecutionDate + Amount per date).
- Optional (set in one consent, omitted in the other): MaximumCumulativeValueOfPayments, MaximumCumulativeNumberOfPayments.
You will provide, for each of the two consents, the pre-production ConsentId, the consent details (the ControlParameters / authorization_details), and a screenshot of the authorization screen the customer saw for that consent.
Fixed Defined Schedule builds on Single Instant Payment. You will be asked for the JIRA ticket of your completed Single Instant Payment certification, so have it to hand.
One ZIP to attach to your ticket
When you have filled in the form and attached your authorization-screen screenshots, the portal generates a single ZIP containing a summary document and every screenshot. Attach it to a Service Desk certification-evidence ticket. Nothing is sent anywhere until you attach it — the submission is built entirely in your browser.