You should choose this if you want to:
- Re-use existing identification for subscription-related transactions
- Enable actions on transaction overview
Depending on your own functionality and how you integrate with us, you might choose to identify subscriptions without our involvement. If that's the case, your way of modelling merchants needs to be synchronised with ours in order to enable the user to take actions on the subscriptions you have identified.
When you identify a merchant, this needs to be mapped to the merchant on our side in order to correctly expose the actions available for this merchant. Our endpoint allows you to retrieve all merchants and their services for exposure in your application. We provide a range of available identifiers, both defined by us but also based on payment attributes (such as credit card identifiers), which makes the lookup simpler for you.
Our list of merchants is constantly improved and should not be stored for long periods of time without being updated. For example, we might add new merchants, remove merchants no longer in business, or update existing merchants with more available actions, sometimes rendering the actions available to your customers irrelevant or non-functional. It is therefore recommended that you synchronise merchants (and optionally, services) with us regularly, preferably multiple times per day.
The process of synchronizing merchants is shown below; this suggestion is based on you fetching and matching our merchant database with your own existing merchants. This enables you to assign actions to subscriptions you identify. Each subscription can be associated with a number of transactions, each of which can now be highlighted for the user with an entry point.
Updated about 1 year ago