Release candidate
v2.2-rc2 is not ratified and MUST NOT be used for production. Current: v2.1. Changelog
This is v2.2-rc2 — a release candidate for the v2.2 standards, published for review and not yet ratified. It MUST NOT be used as the basis for a production implementation. For the current standards, switch to v2.1 using the version selector. See the v2.1 → v2.2-rc2 changelog for every change in this version.
Validate · Enforce · Trust
Payment Refunds — Requirements v2.2-rc22 min read
The tables below list the rules that apply to the Payment Refunds endpoint. The Hub validates authorization and consent permissions before calling your Ozone Connect server — your LFI is responsible for retrieving and returning the debtor's account details.
01 Endpoint
Get Refund
GET
/payment-consents/{consentId}/refund#
Condition
Rule
1
Refund account request received from Hub
Return
200 with a data object containing refundAccount and accountStatus. The refundAccount must include the debtor's schemeName (always IBAN), identification (the debtor's IBAN), and name (an object with en or ar).2
Any
200 responsePopulate
accountStatus with the status of the account in refundAccount, using the statuses that apply to current and savings accounts, with the same meanings as status on GET /accounts/{accountId}: Active, Inactive, Dormant, Unclaimed, Deceased, Suspended or Closed. The Hub returns it to the TPP as AccountStatus.3
Account not
ActiveReturn the refund account regardless of its status, as
GET /accounts does. An account that is Inactive, Dormant, Suspended, Unclaimed, Deceased or Closed MUST still be answered with 200 under rows 1 and 2 — accountStatus reflects its state so the TPP can observe it. Do not return 403 because the account is blocked from receiving payments.