Here is an example of payment process valid for the payment methods CB, VISA and MASTERCARD.

1.To record your customer payment details, you should redirect them to Sherlock’s Paypage, sending the transaction details in the request (amount, currency, etc.), as well as the customer ID (merchantWalletId field).

2.Sherlock's displays the payment page, the customer provides their payment details then confirms.

3. Sherlock's proceeds with 3-D Secure verification.

4. Sherlock's makes anti-fraud checks.

5. Sherlock's sends an authorisation request to the acquirer

6. Sherlock's records the transaction in the back office

7. If the transaction is approved Sherlock's records the customer payment details in the wallet.

8. Sherlock's displays the payment receipt page with a confirmation message that the customer payment method has been recorded.

9. Sherlock's returns the manual and automatic responses containing the transaction details, including the result of customer registration in the wallet.

10. Sherlock's may or may not send the transaction for remittance, depending on the settings that you have configured in the payment request.

The sequence described above applies to the Amex, Bancontact, and PayPal payment methods.

To enrol a customer for the service via Sherlock’s Paypage, you should populate the fields below:

Please refer to one of the Sherlock’s Paypage guides corresponding to the selected connector (JSON, POST or SOAP) to learn how to populate the request, depending on your business requirement.

Sherlock's returns a typical Sherlock’s Paypage manual and automatic response.

The following fields are related to the customer enrolment:

You manage the data entry for payment methods on your website.

1. Step 1: You send a request to Sherlock's to verify the payment method before enrolling the customer.
   • The 3-D secure authentication to verify that the customer is the cardholder of CB, Visa, Mastercard, Amex, Bancontact cards.
   • Anti-fraud checks that you have configured according to your business rules (e.g. foreign cards, commercial cards, etc.).
   • Authorisation request to the acquirer to verify that the card is still valid (not stolen, lost etc.).
     1. Sherlock's records the transaction.
     2. Sherlock's may or may not send the transaction for remittance to the acquirer, depending on the elements provided in the request.
   • Sherlock's sends you the results of the payment methods verification.

2. Step 2: Once the payment method has been verified, you send a second request to Sherlock's to register the payment method in the wallet.

3. Sherlock's returns the payment method registration response.

The sequence described above applies to the Amex, and Bancontact means of payment.

Use the methods below, depending on the verification level of the payment method to be enrolled.

CB, Visa, Mastercard, Bancontact, Oney, AMEX cards

Please refer to one of the Sherlock’s Office guides corresponding to the selected connector (JSON or SOAP), as well as the Payment methods guides, to learn how to populate the request, depending on your business requirements.

cardValidateAuthentication method

When receiving the answer, before analysing it and following the advice in the table below, check the seal. The recalculated seal must be identical to the seal received.

CardOrder, cardValidateAuthenticationAndOrder and directDebitOrder methods

Use the methods below, depending on the payment method to be enrolled. The merchantWalletId field contains the customer ID.

Carte CB, Visa, Mastercard, Bancontact, Oney, Amex

Please refer to the adequate Sherlock’s Office guide, as well as the Payment methods guides, to learn how to populate the request, depending on your business requirements.

1. During the process of enrolling your customers, you redirect them to Sherlock's Walletpage to enter their payment details. Customers select a payment method, provide their payment details, then confirm.

2. Sherlock's proceeds with 3-D Secure verification.

3. Sherlock's makes anti-fraud checks.

4. Sherlock's sends an authorisation request to the acquirer (which does not lead to a payment).

5. Sherlock's records the payment method data in the wallet if the anti-fraud checks are OK and the authorisation is accepted.

6. Sherlock's displays the home page containing a confirmation message. Customers can then see their payment method on the home page.

7. Sherlock's returns the manual and automatic responses containing the wallet content.

Walletpage is the interface that allows customers to manage their wallets. To enrol a customer for the service via Sherlock's Walletpage, you should populate the fields below:

Please refer to the Sherlock's Walletpage guide corresponding to the selected connector (JSON, POST or SOAP) to learn how to populate the request, depending on your business requirements.

Sherlock's returns a manual and an automatic response. The 2 responses are sent through 2 different URLs. The automatic response is always sent, as soon as the URL has been filled in the wallet management request. The information contained in the manual and automatic responses is strictly identical.

The registration of a card in the wallet is a 4-step process:

• checking the 3-D Secure enrollment of the customer's card
• redirecting the customer to their bank's ACS
• sending the 3-D Secure authorisation request (with or without payment)
• adding the card in the wallet

Please refer to the 3-D Secure guide.

You initialise the payment using the walletInitialize method. Apart from the mandatory data of this method, here are the request data you need to pay attention to.

If the initialisation of the registration request has succeeded, send the request via the addCard method of the Sherlock’s In-App SDK. Apart from the mandatory data of this method, here are the request data you need to pay attention to.

1. You redirect the customer to Sherlock’s Paypage, sending the transaction data in the request (amount, currency, etc.), as well as the unique customer ID (merchantWalletId field).

2. Sherlock's displays the payment page, the customer provides their payment method, enter the security code, then confirms.

3. Sherlock's proceeds with 3-D Secure verification

4. Sherlock's makes anti-fraud checks

5. Sherlock's sends an authorisation request to the acquirer.

6. Sherlock's records the transaction in the back office.

7. Sherlock's displays the payment ticket page with a payment confirmation message.

8. Sherlock's returns the manual and automatic responses containing the transaction details, including the result of the customer registration in the wallet.

9. Sherlock's may or may not send the transaction for remittance, depending on the parameters that you have configured in the payment request.

To offer payment via Sherlock’s Paypage, you should fill the fields below:

Please refer to one of the Sherlock’s Paypage guide corresponding to the selected connector (JSON, POST or SOAP) to learn how to enter the request, depending on your business requirement.

Sherlock's returns a typical Sherlock’s Paypage manual and automatic response.

The fields related to a OneClick payment are as follows:

In response to the payment request to the financial establishment, any reply code associated with a fraud risk, or a reply code indicating that the payment method can never be used, will trigger the automatic deletion of the payment method from the wallet. See below for the list of the codes concerned (acquirerResponseCode field):

A 3-D Secure payment from a customer identifier is made in 4 steps:

• authenticating your customer and the means of payment they select in their wallet
• checking the selected card enrollment
• redirecting the customer to their bank's ACS
• the 3-D Secure authorisation request

If your webshop is not a 3-D Secure one, please get in touch with the Sherlock's technical support to activate the service.

To implement a 3-D Secure OneClick payment, you must implement the messages received and sent by the "E-commerce server" entity in the above chart.

A 3-D Secure payment from a customer identifier is made in 4 steps:

• authenticating your customer and the means of payment they select in their wallet
• checking the selected card enrollment
• redirecting the customer to their bank's ACS
• the 3-D Secure authorisation request

If your shop does not have 3-D Secure authentication, please contact the Sherlock's technical support to activate the service.

In order to accept a 3-D Secure card payment, you have to implement the messages received and transmitted by the entities named "E-Commerce Server" and "Mobile App" in the diagram above.

1. You send a credit request using the walletCreditHolder method, sending the transaction data in the request (amount, currency, etc.), as well as the unique customer ID (merchantWalletId and paymentMeanId fields).

2. Sherlock's retrieves the customer payment details stored and sends an authorisation request to the acquirer

3. Sherlock's records the transaction in the back office.

4. Sherlock's returns the response to the credit request.

5. Sherlock's may or may not send the transaction for collection, the same evening.

To credit a customer using the walletCreditHolder method, you should populate the fields below:

Please refer to the Sherlock’s Office guide corresponding to the selected connector (JSON or SOAP) to learn how to populate the other fields for the request, depending on your business requirements.

You can delete a payment method for a customer account via the Sherlock's Gestion. This feature is protected by the access rights assigned to you upon registration. If you need this feature, but you don't have the access rights, please contact technical support.

Immediately

• Submit an enrolment request based on the enrolment scenario that you have chosen (Sherlock’s Paypage, Sherlock’s Office or Sherlock's Walletpage).

Immediately

• Submit a debit request based on the debit scenario that you have chosen (Sherlock's, Sherlock’s Paypage or Sherlock’s Office).
• View the transaction via Sherlock's Gestion, using the transactionReference or S10transactionId.

The next day

• Check that the transaction appears in the transactions report.
• Check your business account to make sure that the operation has been credited.
• If you wish, you can refund the transaction via Sherlock's Gestion.

Two days later

• Check that the refund operation appears in the operations report.
• Check the debit on your merchant account after the refund.

Immediately

• Submit one or several wallet management requests based on the debit scenario that you have chosen (Sherlock’s Paypage, Sherlock's Walletpage, Sherlock’s Office or Sherlock's Gestion).

During the day

• Monitor acceptance rates (number of responseCode 00 per total number of transactions).
• Check the nature of non-banking refusals.
  • Technical problem: responseCode 90, 97, 99
  • Fraud: responseCode 34, 3-D Failure
  • Maximum number of payment attempts reached: responseCode 75

The next day

• Check that all transactions processed (accepted and refused) appear in the transactions report.
• Check the operations you have made and remittances (if you have chosen this report option) in the operations report.

When you submit your first customer debits via Sherlock’s Paypage or Sherlock’s Office:

• Monitor acceptance rates (number of responseCode00 per total number of transactions).
• Check the nature of non-banking refusals.
  • Technical problem: responseCode 90, 97, 99
  • Acquirer fraud: responseCode 34