Neteller Deposit
Neteller is a popular e-Wallet payment method offered in various countries throughout Europe.
The following method IDs are covered in this section:
| ID | Name | Credit/Debit State |
|---|---|---|
| 4 | NetellerDeposit | ExecutedByProvider (142) |
Payment method interaction type: Synchronous execution (see Interaction Types).
Redirect Integration
Supported.
Backend2BackendIntegration - Neteller Balance Enquiry
For the Neteller balance enquiry getPaymentInputData is called by the merchant.
3 types of input request.
- Input Request with only NetellerAccountIdentifier
- Input Request with only paymentAccountID
- Input Request with paymentAccountID,ServiceCode,HomePageUrl
The following table contains the fields to be sent in the getPaymentInputData.Details xml section:
| key (value type, account type, required) | value |
|---|---|
| PaymentAccountID (string) | The unique id of the payment account in PS |
| ServiceCode (string) | The authorization code to access the Neteller account |
| HomePageUrl (string) | URI used during generation of the authorization code |
| NetellerAccountIdentifier (string) | AccountID or EMail address at Neteller |
<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:pay="http://www.cqrpayments.com/PaymentProcessing">
<soapenv:Header/>
<soapenv:Body>
<getPaymentInputDataRequest xmlns="http://www.cqrpayments.com/PaymentProcessing" xmlns:xsd="http://www.w3.org/2001/XMLSchema">
<merchantID>YourMerchantID</merchantID>
<shopID>YourShopID</shopID>
<user>
<id>7777777777</id>
</user>
<paymentMethodID>4</paymentMethodID>
<details>
<data xsi:type="keyStringValuePair" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<key>NetellerAccountIdentifier</key>
<value>450824016049</value>
</data>
</details>
</getPaymentInputDataRequest>
</soapenv:Body>
</soapenv:Envelope>
<s:Envelope xmlns:s="http://schemas.xmlsoap.org/soap/envelope/" xmlns:u="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd">
<s:Header>
<o:Security s:mustUnderstand="1" xmlns:o="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd">
<u:Timestamp u:Id="_0">
<u:Created>2015-10-14T05:18:21.007Z</u:Created>
<u:Expires>2015-10-14T05:23:21.007Z</u:Expires>
</u:Timestamp>
</o:Security>
</s:Header>
<s:Body>
<getPaymentInputDataResponse xmlns="http://www.cqrpayments.com/PaymentProcessing">
<paymentInputData>
<data xsi:type="keyStringValuePair" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<key>AccountID</key>
<value>450824016049</value>
</data>
<data xsi:type="keyStringValuePair" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<key>Email</key>
<value>[email protected]</value>
</data>
<data xsi:type="keyStringValuePair" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<key>FirstName</key>
<value>INRFirstname</value>
</data>
<data xsi:type="keyStringValuePair" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<key>LastName</key>
<value>INRLastname</value>
</data>
<data xsi:type="keyStringValuePair" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<key>DateOfBirth</key>
<value>01/01/1984</value>
</data>
<data xsi:type="keyStringValuePair" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<key>Country</key>
<value>GB</value>
</data>
<data xsi:type="keyStringValuePair" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<key>VerificationLevel</key>
<value>11</value>
</data>
</paymentInputData>
</getPaymentInputDataResponse>
</s:Body>
</s:Envelope>
<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:pay="http://www.cqrpayments.com/PaymentProcessing">
<soapenv:Header/>
<soapenv:Body>
<getPaymentInputDataRequest xmlns="http://www.cqrpayments.com/PaymentProcessing" xmlns:xsd="http://www.w3.org/2001/XMLSchema">
<merchantID> YourMerchantID</merchantID>
<shopID>YourShopID</shopID>
<user>
<id>99999</id>
</user>
<paymentMethodID>4</paymentMethodID>
<details>
<data xsi:type="keyStringValuePair" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<key>PaymentAccountID</key>
<value>323232</value>
</data>
</details>
</getPaymentInputDataRequest>
</soapenv:Body>
</soapenv:Envelope>
<s:Envelope xmlns:s="http://schemas.xmlsoap.org/soap/envelope/" xmlns:u="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd">
<s:Header>
<o:Security s:mustUnderstand="1" xmlns:o="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd">
<u:Timestamp u:Id="_0">
<u:Created>2015-10-14T05:19:24.418Z</u:Created>
<u:Expires>2015-10-14T05:24:24.418Z</u:Expires>
</u:Timestamp>
</o:Security>
</s:Header>
<s:Body>
<getPaymentInputDataResponse xmlns="http://www.cqrpayments.com/PaymentProcessing">
<paymentInputData>
<data xsi:type="keyStringValuePair" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<key>AccountID</key>
<value>458591047553</value>
</data>
<data xsi:type="keyStringValuePair" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<key>Email</key>
<value>[email protected]</value>
</data>
<data xsi:type="keyStringValuePair" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<key>FirstName</key>
<value>GBPFirstname</value>
</data>
<data xsi:type="keyStringValuePair" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<key>LastName</key>
<value>GBPLastname</value>
</data>
<data xsi:type="keyStringValuePair" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<key>DateOfBirth</key>
<value>03/01/1978</value>
</data>
<data xsi:type="keyStringValuePair" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<key>Country</key>
<value>GB</value>
</data>
<data xsi:type="keyStringValuePair" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<key>VerificationLevel</key>
<value>11</value>
</data>
</paymentInputData>
</getPaymentInputDataResponse>
</s:Body>
</s:Envelope>
<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:pay="http://www.cqrpayments.com/PaymentProcessing">
<soapenv:Header/>
<soapenv:Body>
<getPaymentInputDataRequest xmlns="http://www.cqrpayments.com/PaymentProcessing" xmlns:xsd="http://www.w3.org/2001/XMLSchema">
<merchantID> YourMerchantID</merchantID>
<shopID>YourShopID</shopID>
<user>
<id>99999</id>
</user>
<paymentMethodID>4</paymentMethodID>
<details>
<data xsi:type="keyStringValuePair" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<key>PaymentAccountID</key>
<value>323232</value>
</data>
<data xsi:type="keyStringValuePair" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<key>ServiceCode</key>
<value>0.AAAAAVBhU20bAAAAAAAEk-BpbN6wnhmcozNKE0QVKqtS.K0dG-4WLMDqNhKW257Uj7Rn0RqE</value>
</data>
<data xsi:type="keyStringValuePair" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<key>HomePageUrl</key>
<value>https://www.mysite.com/cashier</value>
</data>
</details>
</getPaymentInputDataRequest>
</soapenv:Body>
</soapenv:Envelope>
<s:Envelope xmlns:s="http://schemas.xmlsoap.org/soap/envelope/" xmlns:u="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd">
<s:Header>
<o:Security s:mustUnderstand="1" xmlns:o="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd">
<u:Timestamp u:Id="_0">
<u:Created>2015-10-13T13:12:12.680Z</u:Created>
<u:Expires>2015-10-13T13:17:12.680Z</u:Expires>
</u:Timestamp>
</o:Security>
</s:Header>
<s:Body>
<getPaymentInputDataResponse xmlns="http://www.cqrpayments.com/PaymentProcessing">
<paymentInputData>
<data xsi:type="keyStringValuePair" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<key>AccountID</key>
<value>458591047553</value>
</data>
<data xsi:type="keyStringValuePair" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<key>Email</key>
<value>[email protected]</value>
</data>
<data xsi:type="keyStringValuePair" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<key>FirstName</key>
<value>GBPFirstname</value>
</data>
<data xsi:type="keyStringValuePair" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<key>LastName</key>
<value>GBPLastname</value>
</data>
<data xsi:type="keyStringValuePair" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<key>DateOfBirth</key>
<value>03/01/1978</value>
</data>
<data xsi:type="keyStringValuePair" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<key>Country</key>
<value>GB</value>
</data>
<data xsi:type="keyStringValuePair" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<key>VerificationLevel</key>
<value>11</value>
</data>
<data xsi:type="keyStringValuePair" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<key>Amount</key>
<value>547424255.19</value>
</data>
<data xsi:type="keyStringValuePair" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<key>Currency</key>
<value>GBP</value>
</data>
</paymentInputData>
</getPaymentInputDataResponse>
</s:Body>
</s:Envelope>
Backend2BackendIntegration
The following table contains the fields to be sent in the initiatePaymentRequest.specificPaymentAccountData xml section:
| key (value type, account type, required) | value |
|---|---|
| AccountID (string, required) | User’s account ID for Neteller provider |
| AccountVerificationCode (string, required) | Account’s verification code (like CVC for credit cards) |
There are no specificPaymentData.
Example initiatePaymentRequest:
<initiatePaymentRequest xmlns="http://www.cqrpayments.com/PaymentProcessing" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema">
<merchantID>YourMerchantID</merchantID>
<shopID>YourShopID</shopID>
<merchantTransactionID>3e11b2f1-1d92-4ddd-8d43-9de4e77e4118</merchantTransactionID>
<paymentMethodID>4</paymentMethodID>
<amount currencyCode="EUR">15</amount>
<userID>d48693ca-e96e-4ca1-9e01-435115a79344</userID>
<userData></userData>
<userIP>127.0.0.1</userIP>
<userSessionID>9a156eae-d903-4a01-8170-20dae92673d3</userSessionID>
<creationTypeID>1</creationTypeID>
<paymentAccountID>3fs11u2ve4m89a4yfyd6jdf</paymentAccountID>
<paymentAccount>
<isVisible>false</isVisible>
<specificPaymentAccountData>
<data xsi:type="keyStringValuePair">
<key>AccountID</key>
<value>1234567890</value>
</data>
<data xsi:type="keyStringValuePair">
<key>AccountVerificationCode</key>
<value>12345</value>
</data>
</specificPaymentAccountData>
</paymentAccount>
</initiatePaymentRequest>
Example initiatePaymentResponse:
<initiatePaymentResponse xmlns="http://www.cqrpayments.com/PaymentProcessing">
<payment>
<merchantID>YourMerchantID</merchantID>
<shopID>YourShopID</shopID>
<paymentMethod>
<key>4</key>
<value>NETeller Deposit</value>
</paymentMethod>
<merchantTransactionID>3e11b2f1-1d92-4ddd-8d43-9de4e77e4118</merchantTransactionID>
<paymentID>667d5032-335e-462c-9244-fa8bc7a9f441</paymentID>
<userID>d48693ca-e96e-4ca1-9e01-435115a79344</userID>
<paymentProvider>
<key>21</key>
<value>Neteller</value>
</paymentProvider>
<amount currencyCode="EUR">15</amount>
<creationType>
<key>1</key>
<value>User</value>
</creationType>
<userIP>127.0.0.1</userIP>
<state>
<id>b118842e-0b77-4e4f-803d-144b47b2d977</id>
<definition>
<key>142</key>
<value>ExecutedByProvider</value>
</definition>
<createdOn>2011-05-18T16:14:32.2575197Z</createdOn>
<paymentStateDetails xsi:nil="true" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"></paymentStateDetails>
</state>
<isExecuted>true</isExecuted>
<baseAmount currencyCode="EUR">15.00</baseAmount>
<paymentDetails xsi:nil="true" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"></paymentDetails>
</payment>
</initiatePaymentResponse>
The following result states apply to the payment method NetellerDeposit:
| Payment States | Description |
|---|---|
| ExecutedByProvider (142) | Success state; redirect user to SuccessfulPageUrl |
| ProviderCommunicationErrorOccurred (233) | Error state; Communication error during payment finalization |
| RefusedByProvider (100) | Error state, payment was not accepted by provider; redirect user to ErrorPageUrl. |
| BlockedByPaymentScoring (202) | Error state; Refused by the Kalixa Risk System |
| RefusedByPaymentScoring (121) | Error state; Refused by the Kalixa Risk System |
Notifications
The standard notification mechanism is used for notifying the merchant in the background (asynchronously) about payment state changes. For more information see PaymentStateChangedNotification.
In the Merchant Notification message “UserFirstName”, “UserLastName” and “UserEmail” parameters will be sent (in the paymentAccount.details collection the elements with “userFirstName”, “userLastName” and “userEmail” keys)
Example handlePaymentStateChangedNotificationRequest:
<?xml version="1.0" encoding="utf-8"?>
<handlePaymentStateChangedNotificationRequest
xmlns="http://www.cqrpayments.com/PaymentProcessing"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:xsd="http://www.w3.org/2001/XMLSchema">
<payment xsi:type="paymentWithPaymentAccount">
<merchantID>KalixaAcceptDEMO</merchantID>
<shopID>KalixaAcceptDEMO</shopID>
<paymentMethod>
<key>4</key>
<value>NETeller Deposit</value>
</paymentMethod>
<merchantTransactionID>20141211_5</merchantTransactionID>
<paymentID>3a5eff92-3d62-4b8f-bcb1-5cd8a7f56637</paymentID>
<userID>KalxiaTestUser_3</userID>
<paymentProvider>
<key>21</key>
<value>Neteller</value>
</paymentProvider>
<amount currencyCode="GBP">10.0000</amount>
<creationType>
<key>1</key>
<value>User</value>
</creationType>
<userIP>195.72.132.1</userIP>
<state>
<id>6afcb3d1-78d5-427d-aafa-b6a7733510b5</id>
<definition>
<key>142</key>
<value>ExecutedByProvider</value>
</definition>
<createdOn>2014-12-11T15:33:46.52</createdOn>
<paymentStateDetails xsi:nil="true" />
</state>
<isExecuted>true</isExecuted>
<baseAmount currencyCode="EUR">12.6500</baseAmount>
<paymentDetails>
<detail xsi:type="keyStringValuePair">
<key>ProviderExternalID</key>
<value>711216</value>
</detail>
<detail xsi:type="keyIntValuePair">
<key>PaymentScoring</key>
<value>711216</value>
</detail>
<detail xsi:type="keyStringValuePair">
<key>NetellerUserFirstName</key>
<value>TestFirstName</value>
</detail>
<detail xsi:type="keyStringValuePair">
<key>NetellerUserLastName</key>
<value>TestLastName</value>
</detail>
<detail xsi:type="keyStringValuePair">
<key>NetellerUserEmail</key>
<value>[email protected]</value>
</detail>
<detail xsi:type="keyStringValuePair">
<key>ProviderTransactionID</key>
<value>635539088264118179</value>
</detail>
</paymentDetails>
<paymentAccount>
<paymentAccountID>906004704</paymentAccountID>
<details>
<detail xsi:type="keyStringValuePair">
<key>accountID</key>
<value>224455667788</value>
</detail>
<detail xsi:type="keyStringValuePair">
<key>userFirstName</key>
<value>TestFirstName</value>
</detail>
<detail xsi:type="keyStringValuePair">
<key>userLastName</key>
<value>TestLastName</value>
</detail>
<detail xsi:type="keyStringValuePair">
<key>userEmail</key>
<value>[email protected]</value>
</detail>
</details>
</paymentAccount>
</payment>
</handlePaymentStateChangedNotificationRequest>
Provider Error Codes
| ProviderResponseCode | ProviderResponseMessage |
|---|---|
| 5001 | Invalid currency - The submitted an currency code is invalid or your account does not support this currency. |
| 5010 | Invalid country - The submitted country code is invalid. |
| 5016 | Account not found - The account you provided cannot be found. |
| 5017 | Account disabled - The account you provided is disabled. |
| 5023 | Bad request - The request is not parseable. |
| 5042 | Invalid merchant reference - This error usually indicates that a transaction was attempted with the merchant reference field missing. This value is mandatory and must be included with your request. |
| 5068 | Invalid field - Either you submitted a request that is missing a mandatory field or the value of a field does not match the format expected. |
| 5275 | Authentication credentials expired - The authentication credentials provided with the request have expired. |
| 5276 | Authentication credentials disabled - The authentication credentials provided with the request provided have been disabled. |
| 5277 | Authentication credentials locked - The authentication credentials provided with the request have been locked due to multiple authentication failures. |
| 5278 | Cannot authenticate - The authentication credentials provided with the request were not accepted for an unknown reason. |
| 5279 | Authentication credentials are invalid - The authentication credentials are invalid. |
| 5270 | Unauthorized access - The credentials provided with the request do not have permission to access the requested data. |
| 5269 | Entity not found - The ID(s) specified in the URL do not correspond to the values in the system. |
| 5273 | URI not found - Your client reached our application but we were unable to service your request due to an invalid URL. |
| 5271 | Unsupported 'Accept' header - You requested a response in the 'Accept' header that is in an unsupported format. |
| 5272 | Unsupported 'Content-Type' - The 'Content-Type' you specified in request header was submitted in an unsupported format. |
| 1200 | API call rate exceeded - The API call has been denied as it has exceeded the permissible call rate limit. |
| 1000 | Internal error - An internal error occurred. |
| 1002 | Internal error - Database Error |
| 1003 | Internal error - Decryption Error |
| 1007 | Internal error - Gateway Error |
| 20000 | Unsupported API request - You are not registered to use this API |
| 20001 | Account closed - The account is closed |
| 20002 | Merchant account inactive - Your merchant account is currently inactive. |
| 20003 | Invalid merchant account currency - Your NETELLER Merchant Account does not support this currency. |
| 20005 | Duplicate transaction reference - The provided transaction reference has already been used for another transaction. You must provide a unique value for each request. |
| 20006 | Invalid amount format - Amount must be numeric and cannot contain decimals or any alpha characters. |
| 20007 | Invalid accountId or email - The specified accountId or email is invalid. |
| 20008 | Invalid verification code The supplied verification code was not valid for this request. |
| 20010 | Merchant blocked geolocation - Member is residing in a blocked country/state/region (merchant has chosen to block members from transacting in that location) |
| 20011 | NETELLER blocked geolocation - Member is residing in a NETELLER blocked country/state/region. |
| 20015 | Member is not entitled. - Member is not entitled to receive this type of transaction. |
| 20016 | Merchant is not entitled. - Merchant is not entitled to initiate this type of transaction. |
| 20020 | Insufficient balance - Insufficient balance to complete the transaction. |
| 20021 | Below member min transfer amount - The specified amount is below defined minimum transfer limits. |
| 20022 | Above max transfer out amount - The specified amount is above defined maximum transfer out limits. |
| 20025 | Below merchant min transfer amount - The specified amount is below your defined minimum transfer limits. |
| 20026 | Above max transfer in amount - The specified amount is above defined maximum transfer in limits. |
| 20030 | Below min transaction limit - The specified amount is too low. You must specify an amount greater than or equal to 1 unit of currency. |
| 20031 | Above max transaction limit - The specified amount is too high. You must specify an amount within your transactional limit. |
| 20035 | Above max account limit - The transaction exceeds allowed account limits. |
| 20040 | Expired - The transaction was not completed in the permitted time and has expired. |
| 20045 | Merchant declined - Transaction was manually cancelled or declined by the merchant. |
| 20050 | Legacy transaction details not available from this API, use NetCheck - The transaction you are trying to retrieve was submitted using the legacy NetDirect or Instant Payout API. Please use NetCheck to retrieve the associated error detail for the transaction. |
| 20100 | Plan already exists - The requested planId has already been used. Please specify a unique planId with your request. |
| 20101 | Cannot delete a subscribed to plan - You cannot delete a subscription plan that has already been subscribed to. If you wish to prevent further enrollment in this plan then you must cancel the plan . |
| 20102 | Invalid term length - The term length for this subscription plan is invalid. Please ensure the interval, interval type and interval count combination is less than 5 years. |
| 20200 | Existing member email - The supplied email is already registered with NETELLER. |
| 20900 | Request not authorized - Your request was not authorized as the API requires member authorization. Please use the authorization_grant flow to obtain member permission for the required scope. |
Updated about 3 years ago