William Obam
Chapter 1
1.1 Sign up to a developer Account
Our sandbox environment is open to you after email verification. It can take up to one minute. It is easy to use and convenient, as you can always retrieve your account.
1.2 Create a new Application
The developer portal’s App manager is the perfect playground for testing our solution. As a verified customer, you can also create production applications. Each application has its own. You can create different types of applications depending on the license ownership. You can also make several applications of the same category to cover other entities/use cases. Each application generates a “Client ID” and a client secret. Remember that for the onboarding workflow to be functional, you must list your redirect URLs for safe listing.
Chapter 2
2.1 Import our test collection
Access our Open Banking API doc using the “Documentation” button on the left-hand side of the developer portal. There, we split content per product. Here is the product we refer to as part of this video: https://developer.mastercard.com/open-banking-europe/documentation/unlicensed/aiia-data/quickstart/
Look for “Postman collection” to fork our test package to your Postman account. As a developer, you can easily recreate this package from scratch, but this collection allows you to get this through faster. Follow the five preparation steps and get ready to onboard your first user Account.
2.2 Run the Authentication flow
This flow simulates an account registration. Using our demo banks, you can perform all critical steps required for the PSD2 authentication. Follow the seven-step journey until you get to the final confirmation screen. Use a valid email address.
2.3 Exchange codes
This step requires using an HTTP client as a URL redirect. For a successful flow, you will need to safelist the URL of your HTTP client, as indicated in part B.
Once you have completed the account registration test, we will redirect you to this HTTP client’s page, where you can visualize a temporary code. It is an extended code similar to the one shown in the video. You have limited time to exchange this first “code” for the second “Access token”. After that, we recommend swapping the second for a third “refresh token”. Suppose your use case requires continuous access to the account information. You will need to set a recurring prompt on this task.
Chapter 3
3.1 Get Account information
If you have a valid access token, you can pull it for Account Information using the dedicated endpoint. We show you all the accounts registered for the user and the different objects associated with each account.
3.2 Get Transactions
Once you can access accounts, you can use {accountId} to retrieve transactions associated with this account. Our Query Transaction endpoint is available if you need better control over the type of returned transactions.
Have more questions? Submit a request