Netaxept API reference
The Netaxept API (Application Program Interface) supports REST interface (Representational State Transfer) and Web Services. Please select the most suitable interface option for your business. After you have selected the appropriate interface option, click the drop-down menu in the left side header or links below to find the right API calls for performing transactions through Netaxept. Also, familiarize yourself with the steps described in the Payment Flow Outline section to find out in which order you should perform these calls.
Netaxept doesn't provide any proprietary software installed on your server.
Environments and base addresses
Supported TLS versions
TLS 1.2 is the only secure protocol available when connecting towards Netaxept. Please make sure TLS 1.2 is supported and used in your systems for all operations (i.e. Register, Terminal, Process, Query or similar) when communicating with Netaxept (epayment.nets.eu).
You can check your current TLS version by logging into Netaxept Admin https://epayment.nets.eu. In "Transactions" page you will see the Info box with TLS version for each operation.
In REST, the merchant sends API calls to Netaxept using POST or GET method in HTML format and receives responses in XML format. Parameters in these calls need to be URL encoded, otherwise spaces and special characters will break the call and Netaxept won’t receive it in its complete form. There are no versioning issues with the REST API as long as you implement your XML parsing in a non-strict fashion.
Netaxept offers WSDL (Web Service Desciption Language) files which help merchants to easily understand and integrate the API endpoint. These files contain description of the API endpoint, such as the operations supported by the endpoint, input and output parameters of the supported operations, network protocols and serialization formats. The WSDL files can be downloaded below.
- Test Netaxept.svc
- Single WSDL file (excluding GetCardInformation)
- Single WSDL file for GetCardInformation
Whitelisted Web Services platforms
|PHP5||PHP SoapClient (part of the normal PHP5 distribution)|
|WCF||Windows Communication Foundation (part of .NET framework)|
|CXF||Apache CXF services framework|
|ZSI||The Zolera Soap Infrastructure for Python|
|DOTNET20||.NET 2.0 Web References|
|SUDS||Suds lightweight SOAP client for Python|
|JAX-WS||Java API for XML Web Services|
Blacklisted Web Services platforms
|Axis 1||Apache Axis SOAP engine|
|Axis 2||Apache Axis2 Web Services / SOAP / WSDL engine|
All fields in the Netaxept API are validated according to below mentioned validation rules.
Any of characters a-z, A-Z and 0-9 are supported.
Reference values are currently validated on length alone. The max length for the reference value is given in the max length field in API section.
Boolean parameters need to be given in text form; a string set to either "true" or "false" is supported.
Valid base64-encoded values are supported.
URLs that are max 256 characters and start with the string "http://" or "https://" are supported.
Timestamps are returned with the format YYYY-MM-DDTHH:MM:SS.milliseconds+TZ. Time zone is optional. For example: 2017-02-15T14:35:19.305+01:00
The field can contain any printable characters.
The validation of the field is specific for the field and cannot be described in general. Custom fields typically map to enumerations, but can be anything.
The following table lists all possible values for the
PaymentMethod parameter. Learn more about Payment Methods here.
|DanishConsumerCard||Forbrugsforeningen (Danish loyalty card)|
|DanishDebitMasterCard||Mastercard Debit (Danish merchants only)|
|DanishDebitVisa||Visa Debit (Danish merchants only)|
|DanishDinersClubInternational||Diners Club (Danish merchants only)|
|DanishDebitAmericanExpress||American Express (Danish merchants only)|
|DanishDebitMaestro||Maestro (Danish merchants only)|
|BankAxessMobile||BankAxess via mobile app|
|EstonianBankLuminor||Luminor Bank Estonia direct bank|
|EstonianBankSEB||SEB Estonia direct bank|
|EstonianBankSwedbank||Swedbank Estonia direct bank|
|FinishBankAktia||Aktia Finland direct bank|
|FinishBankAlandsbanken||Ålandsbanken Finland direct bank|
|FinishBankHandelsbanken||Handelsbanken Finland direct bank|
|FinishBankNordea||Nordea Finland direct bank|
Invoice and installments
|AfterPay||AfterPay New API integration|
|WalleyB2C||Walley B2C invoice with Walley hosted terminal In pilot use|
|WalleyB2B||Walley B2B invoice with Walley hosted terminal In pilot use|
|GothiaInstallment||AfterPay instalment Will be discontinued|
|GothiaInvoice||AfterPay invoice Will be discontinued|
|Enterpay||Enterpay B-to-B invoice|
Gift cards and prepaid solutions
|GiftCard||Nets gift card / Gavekort - Will be discontinued|
|GiftCardCenter||Gift card center - Will be discontinued|
|iGiveGiftCard||iGive gift card|
|iGivePromoCard||iGive Promo gift card|
|NetsPrepaidCard||Nets Prepaid Card|
|PBSPrepaidCard||Nets Prepaid / PBS gift card - Will be discontinued|
|SB1GiftCard||Sparebank 1 / SB1 gift card|
|SB1GiftCardCenter||Sparebank 1 / SB1 gift card center|
Wallet based payment methods
The following languages can be used in the hosted payment window: