When your type of business and location legally require you to exclude anonymous payment methods, MyPaySafeCard is the only payment option offered at checkout. MyPaySafeCard acts as an e-wallet and can be used for gambling.
After a shopper completes a payment in their MyPaySafeCard account, customer data is sent to Adyen. MyPaySafeCard requires a shopper to provide first name, last name and date of birth, which are verified by PaySafeCard.
You are expected to have this information on file as well, so you can verify it is the same once the data is shared with you by Adyen by one of the below mentioned methods.
If your PaySafeCard transactions are configured to be automatically captured your account must be changed to an Auth. flow. When set to an Auth. flow, your PaySafeCard transactions remain in the status Authorised until you make a capture request. The authorized amount remains frozen for 24 hours, until it is released again to the shopper on their MyPaysafecard account. It's good practice to perform the verification of the customer and executing the capture as quickly as possible to ensure a pleasant customer experience.
Use customer data to determine whether to capture transactions
When a shopper makes a payment from a MyPaySafeCard account, the transaction flow will include:
-
Your shopper logs in to your system.
-
The shopper makes a payment using MyPaySafeCard.
-
The shopper authorizes the transaction. The money is reserved, but not debited yet.
-
During the transaction PaySafeCard sends customer data to Adyen (first name, last name and date of birth).
-
You receive the Customer Data Exchange content from Adyen.
The data is returned from Adyen in one of two ways:
- After the shopper completes the redirect, send the
redirectResultto the /payments/details endpoint to verify that the transaction is authorized and to view the customer’s data. - After the transaction is authorized, listen for the standard webhook notification, which is sent to the endpoint you configure in Customer Area. The webhook contains the customer data in the same format as the /payments/details response.
The account owner's data that is returned:
- first and last name
- date of birth
- ID of the account
- After the shopper completes the redirect, send the
-
Your system compares the information in the user account with the information from the Customer Data Exchange.
-
Your system either cancels the payment with a request to /payments/{paymentPspReference}/cancels (which removes the reservation of the funds on the shopper's MyPaySafeCard account balance), or captures the payment with a request to /payments/{paymentPspReference}/captures.
Configure how the customer data should be returned
Indicate in the Customer Area how the customer data must be returned:
- To receive it in the /payments/details response, go to Developer > Additional Data, and enable “payment account owner data”.
- To receive it in the standard webhook, go to Developer > Webhooks, create a standard webhook, and in “payment” enable “payment account owner data”.
The Customer Data Exchange feature of PaySafeCard can be configured for any currency account via Adyen.
Receive customer data
When the shopper returns from redirect
When the shopper gets redirected back from PaySafeCard after they complete the authorization from their account, a data object is included in the return URL, which you can send to /payments/details:
When the shopper does not return from redirect
If you do not see your shopper return to the front-end, you still receive a standard webhook notification that confirms the authorization of the payment: