Business Overview

Roles

MyBank business cases presented below involve the following roles:

Role	Description
Payer, Buyer, Authorising Party	The subject responsible of authorising a MyBank transaction. The term ‘Buyer’ is used noting that a Buyer can be a consumer, a small business, a medium-sized business or any other organisation that uses a human interface to authorise a purchase or a payment.
Payee, Seller, Merchant	The subject that, in the end, receives the funds of the MyBank transaction. The term ‘Seller’ is used to refer to a ‘merchant’, however it also encompasses actors like charity organisations, public administrations, corporate entities that need to collect payments from Buyers.
Payer PSP, Buyer Bank	The Bank or Payment Service Provider of the Payer that allows him to authenticate and authorise MyBank transactions and underlying payments.
Payee PSP, Seller Bank, Initiating Party	The Bank or Payment Service Provider that, through his connection to the MyBank Gateway, provides Merchants or other PSPs with the MyBank solution.
API Client	The subject technically connected to the MyBank Gateway. It might be the Payer PSP or a subject acting on behalf of the Payer PSP.

Functional Flows

Aim of this section is listing and explaining the set of technical flows that a Payer PSP can implement with the MyBank Gateway APIs.

MyBank Standard Flow

MyBank Standard Flow allows Payer PSPs to process MyBank transactions initiated by participating Payee PSPs.
More specifically, it allows a Payer (known customer of a Payer PSP) to securely authorise a MyBank transaction.

The classic scenario for this flow is the e-commerce use case, which could be described by the following steps:

(a) On the Merchant's checkout page the Payer selects MyBank as payment method.

(b) The Payee PSP shows the list of the available Payer PSPs.

(d) The Payee PSP initiates a MyBank Transaction.

(e) The Payer is redirected to the Payer PSP's environment.

(f) The Payer PSP retrieves the data of the transaction from the MyBank Gateway, by invoking the "Transaction Fetch" API.

(g) The Payer PSP presents the MyBank Login page of the Banking Application to the Payer. It also informs MyBank Gateway that the Login page was visited, by invoking the "Transaction Set Milestone" API.

(h) The Payer authenticates himself on the Banking Application.

(i) The Payer PSP informs MyBank Gateway that the user was authenticated by invoking the "Transaction Set Milestone" API.

(j) The Payer PSP presents the MyBank Authorisation page to the Payer. It also informs MyBank Gateway that the transaction data were displayed, by invoking the "Transaction Set Milestone" API.

(k) The Payer authorises the transaction.

(l) The Payer PSP sets the final status of the transaction, by invoking the "Transaction Set Status" API.

(m) The Payer PSP stores the (irrevocable) payment order (and/or executes the payment) and presents the MyBank Status Confirmation page to the Payer.

(n) The Payer PSP redirects the Payer back to the Merchant's website.

(o) The Payee PSP retrieves the result of the transaction.

(p) The Merchant's website presents the business confirmation message to the Payer.

Details on the required implementation will be provided in the [Implementation Guide].