Put Request to Pay back in order

THE DRILL AS TEXT

1. In Request to Pay, what happens first, and what follows?
   • Example Supplies raises a payment request — Instead of pulling by direct debit, the creditor asks to be paid. It submits a pain.013 request for EUR 120.00 with an invoice reference and a due date through Northstar Bank, its bank.
   • Northstar routes the request via the RtP service — The Request-to-Pay service is a messaging layer, not a money mover. It carries the request from the creditor's side towards the debtor's bank; no funds move at this stage.
   • The request is delivered to Maya's bank — The service delivers the request to Bank Alfa, which presents it to Maya in her banking app — showing who is asking, how much, and by when.
   • Maya accepts, defers, or declines — Control sits with the debtor. Maya can pay now, ask for more time, pay a different amount by agreement, or decline outright. On the happy path she accepts the request in full.
   • Bank Alfa returns Maya's acceptance — A pain.014 response travels back to tell Example Supplies that Maya accepted and payment is coming. The response answers the request; it is not itself the money.
   • Bank Alfa sends a SEPA Instant transfer — Acceptance triggers an ordinary payment. Bank Alfa debits Maya and submits a SEPA Instant credit transfer (a pacs.008) to Northstar Bank — the request has become a normal push payment.