To request permissions, you must set up the URL with the parameters described below and redirect the user to this URL .
After the user grants the permission, you will receive a code to use in a new server-side request to actually receive the access token that will give you the granted access.
redirect_urimust be exactly the same as what was registered when APP was created.
Permission to create and consult ORDERS , PAYMENTS , MULTIORDERS , MULTIPAYMENTS , CLIENTS and consultation of ENTRIES . Permission to obtain the sales reconciliation file.
Permission to create and consult refunds for ORDERS , PAYMENTS .
Permission to consult the information about ACCOUNTS.
Permission to check balance via endpoint ACCOUNTS and obtain the financial conciliation file.
Permission for bank transfers or Wirecard accounts via endpoint TRANSFERS .
Permission to create, change and delete notification preferences via endpoint PREFERENCES .
In order for you to ask permission from sellers you must set up a URL with data such as App id and scopes. Below is an example of a URL with the permissions you want to obtain from your marketplace/platform vendors:
You must redirect your seller to this URL, as this is where the user will grant (or not) permission to access his information.
You can send additional parameters to make the user identification using
query-params, but it is necessary that you encode the URL so that the parameters sent do not conflict with the mandatory parameters.
1. The seller is redirected to the permission request page;
2. at that time Wirecard will check if the customer is logged in. If so, the options to accept or decline the link to your app will be displayed;
3. if permission is granted, the user will be redirected to their redirect URL (
redirect_uri) with the
code referring to the user's confirmation.