KYC notification

In this section we will discover how merchants are able to retrieve KYC data from this notification as well as any market specific requirements around these data points.

Trustly will send a KYC notification to the merchant’s NotificationURL if the attribute "RequestKYC" : “1” is sent in a Deposit API call. The KYC notification should be expected after the player has performed one successful login to their bank and always before a deposit transfer is initiated.

Once the data is processed by the merchant, the merchant will reply to either Allow (CONTINUE) the deposit transfer or Deny (FINISH) the deposit.

In this section we will look at the three possible options you can reply to KYC notifications:

• CONTINUE

• FINISH

• CONTINUE + Limit - Optional response (see Appendix Section CONTINUE with LIMIT response)

CONTINUE response

Most common scenario. Merchant has performed all necessary checks and prompts Trustly to CONTINUE with prompting the player to sign their deposit transfer (or complete login towards their bank if amount is not populated in the Deposit call)

FINISH response

Here are common scenarios where FINISH scenarios are expected:

• Session limit reached

• Player is trying to perform a login+deposit where deposit limit is reached and merchant does not support the Continue + Limit functionality

• Player is self excluded from gambling

• Player is blacklisted from gambling altogether

• Player is blacklisted through other site under same Whitelabel

• Any other scenario should entail the player to be able to CONTINUE through the Trustly checkout flow.

CONTINUE with LIMIT response

See example of “CONTINUE with LIMIT” response.

AbortMessage Data flow

Unverified KYC information

In the rare event that the player’s KYC information is not available, you will not receive this data in the KYC notification. Our experience indicates that this usually only occurs when special restrictions are enforced by the government or enforcement agencies. In that case, you will receive a KYC notification with the following attribute:

"abortmessage": "unverified",

upon which you need to reply with “FINISH”.

Underage detection

If the player is underage, Trustly will send a KYC notification with the following data:

"abortmessage": "underage",

upon which you need to reply with “FINISH”.

For a Pay N Play integration, we recommend that you do regular KYC re-checks to cross check provided player data against your controlled database.

To do that, you need to

• Use attribute RequestKYC: 1 for the login/registration stage and for players that are already logged to avoid deposits from 3rd parties.

• For all markets its recommended to always include logic revolving around KYC data. SSN / Person ID aids in identifying users. KYC data checks can include the following logic:

KYC data logic

{FirstName} AND/OR {LastName} AND/OR {DOB} AND/OR {Street} AND/OR {ZipCode} AND/OR {City} AND/OR {Country}

Note: The end result of the above information aims to guide merchants in making a calculated CONTINUE decision. Please note that it’s up to the merchant’s own interpretation of any Gaming Requirements on how such cases are to be handled. The above acts as a suggestive approach based on past, successful, integrations

Note that for the instance of a previously used bank account, the AccountID provided in the Account Notification will remain the same. Though this data is sent after the deposit is done, merchants may find this aspect useful as they can flag if the player in question used an existing AccountID or not.