Request: (No request body. GET requests do not carry a body. Parameters are in the URL query string: status=ACSC, limit=20, offset=0)
Response: {
"payments": [
{
"payment_id": "PAY-20261105-8841",
"status": "ACSC",
"end_to_end_id": "INV-8841",
"creditor_name": "Tanaka Trading Pte Ltd",
"currency": "USD",
"amount": 25000.0,
"value_date": "2026-11-05"
}
],
"page": {
"limit": 20,
"offset": 0,
"total": 1,
"has_more": false
},
"request_id": "REQ-20261105-0008"
}Lists payments, newest first, with pagination. Use it to reconcile what the bank holds against your own ledger, instead of polling one payment at a time. Responses are pages: always follow the page fields, never assume o
Worked Example: A Customer Pays EUR 240 Through a PISP
What you will learn
Your objective. By the end of this lesson, you will be able to explain worked example: a customer pays EUR 240 through a PISP. Claire Dubois, a customer of Meridian Bank in Lyon, buys EUR 240 of kitchen goods from an online retailer called Maison Nord.
Why it matters. A business analyst should note that the mismatch warning, the consent record, and the authentication record are all stored, because they are the evidence if Claire later disputes the payment.
Chapter objective: How regulated access to bank accounts changed payments
Key learning points
- Customer of Meridian Bank in Lyon
- She agrees
- Bank shows Claire a warning
- Meridian Bank executes the credit transfer
- Retailer bank
Key terms
Settlement: The final movement of funds between banks to discharge obligations created by cleared payments. Settlement is usually made in central bank money or through correspondent accounts.
Clearing: The process of exchanging payment instructions between banks and calculating what each bank owes the others.
PISP: Payment initiation service provider, a licensed provider that initiates payments from a customer account with the customer consent, under open banking rules.
API request and response viewer showing Worked Example: A Customer Pays EUR 240 Through a PISP.
Practise this lesson
Exercise
Write the request and the expected response for the API call described in this lesson.
Use the API resources, operations and fields named in this lesson.
- What to do. Write the JSON request with the required fields, the success response, and one error response with its error code.
Correct result. A correct request has all mandatory fields, a valid idempotency key, and the right resource and operation. The success response confirms acceptance, and the error response names the field or rule that failed.
Why. An API contract is a promise between two systems. If the request is wrong, the API must reject it cleanly, not fail silently.
Check your understanding
Practice question
Which of the following best describes worked example: a customer pays EUR 240 through a PISP?
Takeaway and next step
What to remember
The bank checks her device, her location in Lyon, and her payment history, and it sees that she has never paid Maison Nord before, which raises the risk slightly.
Call the API described in this lesson with a valid request, then with a missing field, and compare the responses.
Builds on "Verification of Payee and Fraud Information Exchange".
Transcript and full text
Show transcript
Claire Dubois, a customer of Meridian Bank in Lyon, buys EUR 240 of kitchen goods from an online retailer called Maison Nord. At checkout she chooses pay by bank, and the retailer PISP, a licensed provider called PayBridge, shows her a list of banks. She picks Meridian Bank, and PayBridge sends an API call to Meridian Bank asking to start a payment of EUR 240 to Maison Nord, with the retailer account number and the order reference. Claire sees a consent screen that names PayBridge, states the amount EUR 240, names the payee Maison Nord, and explains that PayBridge will start one payment and will not read her account history. She agrees, and the consent is recorded with a time stamp. Meridian Bank now runs its fraud checks before it asks Claire to authenticate. The bank checks her device, her location in Lyon, and her payment history, and it sees that she has never paid Maison Nord before, which raises the risk slightly. It then runs verification of payee, comparing the name Maison Nord with the name on the account PayBridge supplied. The check returns a mismatch, because the account is held in the name of Maison Nord SARL Trading, and the trading name does not match the registered name exactly. The bank shows Claire a warning that the name does not fully match, displays the registered name, and asks her to confirm that she still wants to proceed. She checks the retailer website, sees the legal name in the footer, and confirms. Claire now completes strong customer authentication on the Meridian Bank app, using her fingerprint and a one time code, which are two independent factors. The bank links the authentication to the amount EUR 240 and to the payee, so the approval cannot be reused for another payment. Once authentication succeeds, Meridian Bank executes the credit transfer, debiting EUR 240 from Claire account and crediting the Maison Nord account through the SEPA Instant route, because the retailer asked for an instant payment. PayBridge receives a confirmation through the bank API and tells the retailer that the payment has started, and the retailer shows Claire an order confirmation. The whole journey takes under a minute. The ledger entries tell the same story in accounting terms. Meridian Bank debits Claire customer account with EUR 240 and credits its internal settlement account with EUR 240, then settles the EUR 240 through the clearing system to the retailer bank. The retailer bank credits the Maison Nord account with EUR 240 and debits its own settlement account. If the fraud check had blocked the payment, no debit would have happened, and PayBridge would have received a rejection with a reason code. A business analyst should note that the mismatch warning, the consent record, and the authentication record are all stored, because they are the evidence if Claire later disputes the payment. A product owner should note that the warning wording decided the outcome, because a confusing warning would have lost the sale, and a weak warning would have let a fraud through.
Claire Dubois, a customer of Meridian Bank in Lyon, buys EUR 240 of kitchen goods from an online retailer called Maison Nord. At checkout she chooses pay by bank, and the retailer PISP, a licensed provider called PayBridge, shows her a list of banks. She picks Meridian Bank, and PayBridge sends an API call to Meridian Bank asking to start a payment of EUR 240 to Maison Nord, with the retailer account number and the order reference. Claire sees a consent screen that names PayBridge, states the amount EUR 240, names the payee Maison Nord, and explains that PayBridge will start one payment and will not read her account history. She agrees, and the consent is recorded with a time stamp.
Meridian Bank now runs its fraud checks before it asks Claire to authenticate. The bank checks her device, her location in Lyon, and her payment history, and it sees that she has never paid Maison Nord before, which raises the risk slightly. It then runs verification of payee, comparing the name Maison Nord with the name on the account PayBridge supplied. The check returns a mismatch, because the account is held in the name of Maison Nord SARL Trading, and the trading name does not match the registered name exactly. The bank shows Claire a warning that the name does not fully match, displays the registered name, and asks her to confirm that she still wants to proceed. She checks the retailer website, sees the legal name in the footer, and confirms.
Claire now completes strong customer authentication on the Meridian Bank app, using her fingerprint and a one time code, which are two independent factors. The bank links the authentication to the amount EUR 240 and to the payee, so the approval cannot be reused for another payment. Once authentication succeeds, Meridian Bank executes the credit transfer, debiting EUR 240 from Claire account and crediting the Maison Nord account through the SEPA Instant route, because the retailer asked for an instant payment. PayBridge receives a confirmation through the bank API and tells the retailer that the payment has started, and the retailer shows Claire an order confirmation. The whole journey takes under a minute.
The ledger entries tell the same story in accounting terms. Meridian Bank debits Claire customer account with EUR 240 and credits its internal settlement account with EUR 240, then settles the EUR 240 through the clearing system to the retailer bank. The retailer bank credits the Maison Nord account with EUR 240 and debits its own settlement account. If the fraud check had blocked the payment, no debit would have happened, and PayBridge would have received a rejection with a reason code. A business analyst should note that the mismatch warning, the consent record, and the authentication record are all stored, because they are the evidence if Claire later disputes the payment. A product owner should note that the warning wording decided the outcome, because a confusing warning would have lost the sale, and a weak warning would have let a fraud through.
Full lesson text (all scenes)
Completing a lesson updates your progress dashboard on the homepage.
Scene timestamps are estimated by allocating the narration text proportionally across the real audio length. The audio playback position is the source of truth: pause freezes the visual, seeking restores the correct scene, replay restarts the scene animation.