The most important part of issuer data definitions is that the issuer data is created according to your own bank's or institution's developments and application flows. Let us try to explain with examples below:
- Suppose you have created ON-US credit card data for your bank or institution. If you forget to add your ON-US credit card BINs to this data, you may find that the appropriate flows are not created for transactions you make on the POS device with ON-US credit cards,
- You may find that you cannot make installment transactions with your ON-US credit card BINs even though you expect to,
- In transactions made on shared POS or ÖKC POS devices, you may find that your own cards go to other banks' applications even though you expect them to come to your own application,
- If you do not add the BINs that need to be added to the data you created for your brand, you may find that installment, reward points and similar flows are not created,
- On shared POS or ÖKC POS devices, you may find that transactions do not come to your bank application even though you are the only bank for that brand,
- When you sign an agreement with a new card institution, if you do not record the BIN information as a range, you may find that transactions cannot be made on the POS device.
Since all the examples I have given above will affect merchant turnover and therefore the turnover of your bank or institution, attention should be paid to all definitions to be made.
