Product updates

Identify repeat payers with our new webhook notification

We know that there are times when it’s crucial to know when a customer is making multiple purchases or payments, such as to enhance KYC checks or identify if a customer is abusing a promotion. For this reason, this week we are rolling out a new feature to allow our merchants and partners to identify repeat payers.

2 years ago • 2 min read

Why are we introducing this?

For many merchants, it’s not always easy to flag those who are using the same account to make multiple payments, especially if they are using a number of different accounts on your website. Our new notification system takes the guesswork out and allows you to be alerted as soon as a repeat payment is made.

This can be useful in many scenarios:

  • Do you have a signup bonus incentive? You can now identify a customer who is creating multiple new accounts but using the same banking details to claim the promotion.

  • Are you an online retailer selling a product with limited quantities per customer? Get your product out to as many of your customers as possible by being flagged for those who could be abusing the system.

  • Are you required to have enhanced KYC checks? Our notification system allows you to ensure the details you have registered match up to the bank account the payment is coming from.

  • Are you concerned about customer fraud? Vyne’s Pay with bank not only reduces the risk of fraud, it can also help further satisfy audit checks by providing details about the remitter of funds.

How does it work?

To ensure we retain the highest possible levels of security, we are using a webhook notification to share this information with merchants. This means account details can be securely shared without the need of handling payer details. This feature will not be included in reporting, it will be available for use only in a notification capacity so no sensitive information is shared.

How can I enable this feature?

We’ve already rolled out payer identification to all merchants and partners in an existing webhook so no implementation is required. You can read more about the PayerToken field on our developer site.

For merchants who need to see more enhanced information, such as the payer’s name, you will need to get in touch with us to set this up. Read more about how this integration works here.