GuidesAPI ReferenceDiscussions

Neteller Customer Validation

Suggest Edits

The Neteller customer validation service is used to check if the merchants customer, identified by an eMail address, acountID or customerID, is registered with Neteller. The merchant can thus verify information holding about the customer against Netellers´s registration records.

Accounts are active once created by the customer and remain active until closed by either the customer or by Neteller.

The information that is checked can be:

  • eMail address
  • First Name
  • Last Name
  • Date of Birth
  • House Number
  • Country
  • Post Code

🚧

Email address vs. Neteller accountID/ customer ID

If the customer has an active Neteller Wallet account, then the verification service returns a MATCH or NO_MATCH response for each parameter provided in the request.

Match information is not shown by default for the email address. However, If either accountID or Customer ID and email are provided then the customer account is being identified by the accountID (or customerID) and match information is shown for the email.

Backend2BackendIntegration

The following table contains the fields to be sent in the validatePaymentAccount.specificPaymentAccountData xml section:

key (value type, account type, required)value
AccountID
(string, required)		eMail address of Neteller user

The eMail address matching is done against any primary or secondary email addresses registered with Neteller.
SubAccountID (string)Neteller AccountID
CustomerID (string)Neteller customerID

❗️

Passing account data

The field AccountID - to be filled with the customer`s eMail address - is mandatory.

In addition, the merchant may pass SubAccountID (Neteller accountiD) or CustomerID (Neteller customerID).

*If you pass Email and Neteller Account ID = the Neteller system looks up the customer’s account by the account ID and checks whether the email matches as well.

If you pass Email and Customer ID = the Neteller system looks up the customer’s account by the customer ID and checks whether the email matches as well.

If you pass only email = the Neteller system looks up the customer account by the email and checks whether the email matches as well.

If you pass Email, Account ID and Customer ID = the Neteller system returns an error.

If you pass Account ID and Customer ID = the Neteller system returns an error.*

Passing only the SubAccountID (Neteller accountID) is not possible.

Example validatePaymentAccountRequest:

?xml version="1.0" encoding="utf-8"?>
<validatePaymentAccountRequest xmlns="http://www.cqrpayments.com/PaymentProcessing" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
  <merchantID>B2BTestMerchant</merchantID>
  <paymentAccountTypeID>6</paymentAccountTypeID>
  <paymentMethodID>4</paymentMethodID>
  <paymentProviderID>21</paymentProviderID>
  <specificPaymentAccountData>
    <data xsi:type="keyStringValuePair">
      <key>AccountID</key>
      <value>[email protected]</value>
    </data>
    <data xsi:type="keyStringValuePair">
      <key>SubAccountID</key>
      <value>AccountID123</value>
    </data>
	<data xsi:type="keyStringValuePair">
      <key>CustomerID</key>
      <value>12345678</value>
    </data>
  </specificPaymentAccountData>
  <additionalData>
   <data xsi:type="keyStringValuePair">
      <key>firstName</key>
      <value>John</value>
    </data>
    <data xsi:type="keyStringValuePair">
      <key>lastName</key>
      <value>Payer</value>
    </data>
    <data xsi:type="keyDateTimeValuePair">
      <key>DateOfBirth</key>
      <value>1970-12-01T00:00:00</value>
    </data>
    <data xsi:type="keyStringValuePair">
      <key>HouseNumber</key>
      <value>221b</value>
    </data>
    <data xsi:type="keyStringValuePair">
      <key>PostCode</key>
      <value>CR34JP</value>
    </data>
    <data xsi:type="keyStringValuePair">
      <key>Country</key>
      <value>DEU</value>
    </data>
  </additionalData>
</validatePaymentAccountRequest>

When a paymentaccount detail matches, the response is MATCH. When the values do not match, the response include NO_MATCH. In addition a verification level value is returned.

Verification LevelDescription
00- The Neteller customer has not been verified
- The customer has no verified registered payment instruments (Credit/Debit Card or Bank Account)
01- The Neteller customer has not been verified.
- The customer has one or more verified registered payment instruments (Credit/Debit Card or Bank Account)
10- The Neteller customer has been verified
- The customer has no verified payment nstruments (Credit/Debit Card or Bank Account)
11- The Neteller customer has been verified
- The customer has one or more verified payment instruments (Credit/Debit Card or Bank Account)

Example validatePaymentAccountResponse:

<?xml version="1.0" encoding="utf-8"?>
<validatePaymentAccountResponse xmlns="http://www.cqrpayments.com/PaymentProcessing" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
  <statusCode>0</statusCode>
  <validationResults>
    <result xsi:type="keyStringValuePair">
      <key>Email</key>
      <value>MATCH</value>
    </result>
    <result xsi:type="keyStringValuePair">
      <key>FirstName</key>
      <value>MATCH</value>
    </result>
    <result xsi:type="keyStringValuePair">
      <key>LastName</key>
      <value>NO_MATCH</value>
    </result>
    <result xsi:type="keyStringValuePair">
      <key>DateOfBirth</key>
      <value>MATCH</value>
    </result>
    <result xsi:type="keyStringValuePair">
      <key>HouseNumber</key>
      <value>NO_MATCH</value>
    </result>
    <result xsi:type="keyStringValuePair">
      <key>PostCode</key>
      <value>NO_MATCH</value>
    </result>
    <result xsi:type="keyStringValuePair">
      <key>Country</key>
      <value>MATCH</value>
    </result>
    <result xsi:type="keyStringValuePair">
      <key>VerificationLevel</key>
      <value>11</value>
    </result>
  </validationResults>
</validatePaymentAccountResponse>

A customer is listed as verified if at least one of the following apply:

  • Neteller has identification documents on file for the customer
  • Address verification has been completed ‐ either manually or by post
  • The customer has been verified by Tsevo (US customers only)

Payment instrument verified means that the customer has been verified as the legitimate owner of a
listed payment instrument (Debit/Credit Card or Bank Account).

Updated about 4 years ago