Find file Copy path
Fetching contributors…
Cannot retrieve contributors at this time
49 lines (40 sloc) 2.67 KB

Mollie Connect: Getting started

Assuming you have already built an OAuth-compatible app, the first step is to register your app in your Dashboard. You will receive a Client ID and Client Secret, both of which should be kept secret. These credentials can be used to:

  • Redirect users to your app's authorization form (Client ID)
  • Exchange authorization codes for access tokens (Client ID & Client Secret)
  • Renew your access tokens
  • Deauthorize users from your app (Client ID & Client Secret)

Configuring your OAuth app

Use the details below to configure your app to work with our platform.

Getting a merchant’s consent

After having registered and configured your app, you can send the merchant to Mollie through the default authorization URL as configured in your OAuth app. Good practice is to show a Connect with Mollie button which redirects the merchant to :doc:`the authorization screen </reference/oauth2/authorize>`.

When you send a merchant to the authorization screen, Mollie will tell the merchant what data your app has requested access to, and request the merchant to confirm the authorization. An example authorization is shown below.


Working with access tokens

The merchant will be redirected back to your app, along with an auth code. With the auth code, you can retrieve an access token using default OAuth library functionality. Note access tokens are time limited - you need to refresh them periodically using the refresh token.

Have merchants start using your app

Using the access token on the Mollie API, your app may now access the merchant's account data, allowing the merchant to start using your app.

It's possible to retrieve the merchants preferred locale via :doc:`Organization details </reference/v2/organizations-api/get-organization>`. It is recommended to switch your app's locale to the merchant's locale after the OAuth flow.