Functional Certification · Variable Periodic Schedule

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.

Checking your session…

Consent evidence

Evidence two pre-production Variable Periodic Schedule consents — one with every optional control parameter set, one with only the required minimum. For each, share the ConsentId, paste the consent details, and attach the authorization screen linked to it. All evidence must come from the AlTareq Model Bank sandbox.

0 of 2 control-parameter scenarios complete.

Testing Tool output optional

Optionally attach the Testing Tool HTML report for your Ozone Connect payment endpoints. This is not required for Variable Periodic Schedule — the certification is consent-focused — but you may include it as supporting evidence.

Testing Tool report (optional)HTML report from the Testing Tool for your Ozone Connect payment endpoints.

All control parameters set

Create a Variable Periodic Schedule consent with every optional control parameter populated — the consent-level cumulative caps (MaximumCumulativeValueOfPayments). Your authorization screen must surface these limits to the customer.

Reference — example ControlParameters

{
    "IsDelegatedAuthentication": false,
    "ConsentSchedule": {
      "MultiPayment": {
        "MaximumCumulativeValueOfPayments": { "Amount": "12000.00", "Currency": "AED" },
        "MaximumCumulativeNumberOfPayments": 12,
        "PeriodicSchedule": {
          "Type": "VariablePeriodicSchedule",
          "PeriodType": "Month",
          "PeriodStartDate": "2026-08-01",
          "MaximumIndividualAmount": { "Amount": "1200.00", "Currency": "AED" }
        }
      }
    }
  }

Pre-production ConsentIdConsent details paste the ControlParameters / authorization_details for this consent

Authorization screenScreenshot of the authorization screen the customer saw for this consent, showing the control parameters above.

Optional control parameters not set

Create a second Variable Periodic Schedule consent carrying only the required minimum (PeriodType, PeriodStartDate, MaximumIndividualAmount, MaximumCumulativeNumberOfPayments) — omit the optional cap (MaximumCumulativeValueOfPayments). This proves your LFI handles a consent with no optional ceilings. Note the API Hub still requires MaximumCumulativeNumberOfPayments for this type, so it is kept.