Skip to content

    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

    EnvironmentBase address

    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 (

    You can check your current TLS version by logging into Netaxept Admin 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.

    Web Services

    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 environment:

    Production environment:

    Please note that when you programmatically generate stubs from our WSDL files you might run into problems when these WSDL files are updated (and for example fields are added to Netaxept's output parameters).

    To avoid issues as a result of altered output parameters compared to when the stub was generated, make sure your Web Service platform is whitelisted below.

    If your Web Services platform is not on whitelisted or is blacklisted, please refrain from using it against Netaxept, as your Netaxept implementation might break when we make changes.

    The lists below are subject to change.

    Whitelisted Web Services platforms

    PHP5PHP SoapClient (part of the normal PHP5 distribution)
    WCFWindows Communication Foundation (part of .NET framework)
    CXFApache CXF services framework
    ZSIThe Zolera Soap Infrastructure for Python
    DOTNET20.NET 2.0 Web References
    SUDSSuds lightweight SOAP client for Python
    JAX-WSJava API for XML Web Services

    Blacklisted Web Services platforms

    Axis 1Apache Axis SOAP engine
    Axis 2Apache 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.

    Payment methods

    The following table lists all possible values for the PaymentMethod parameter. Learn more about Payment Methods here.

    Payment cards

    AmericanExpressAmerican Express
    DanishConsumerCardForbrugsforeningen (Danish loyalty card)
    DanishDebitMasterCardMastercard Debit (Danish merchants only)
    DanishDebitVisaVisa Debit (Danish merchants only)
    DanishDinersClubInternationalDiners Club (Danish merchants only)
    DanishDebitAmericanExpressAmerican Express (Danish merchants only)
    DanishDebitMaestroMaestro (Danish merchants only)

    Direct banks

    EstonianBankLuminorLuminor Bank Estonia direct bank
    EstonianBankSEBSEB Estonia direct bank
    EstonianBankSwedbankSwedbank Estonia direct bank
    FinishBankAktiaAktia Finland direct bank
    FinishBankAlandsbankenÅlandsbanken Finland direct bank
    FinishBankHandelsbankenHandelsbanken Finland direct bank
    FinishBankNordeaNordea Finland direct bank
    FinishBankOmaSaastopankkiOma Säästöpankki Finland direct bank
    FinishBankOpOP Finland direct bank Will be discontinued

    Invoice and installments

    RivertyRiverty New API integration (formal name: AfterPay)
    CollectorWalley invoice
    CollectorInstallmentWalley installment
    WalleyB2CWalley B2C invoice with Walley hosted terminal In pilot use
    WalleyB2BWalley B2B invoice with Walley hosted terminal In pilot use
    GothiaInstallmentRiverty installment
    GothiaInvoiceRiverty invoice
    EnterpayEnterpay B-to-B invoice

    Gift cards and prepaid solutions

    GiftCardNets gift card / Gavekort - Will be discontinued
    GiftCardCenterGift card center - Will be discontinued
    iGiveGiftCardiGive gift card
    iGivePromoCardiGive Promo gift card
    NetsPrepaidCardNets Prepaid Card
    PBSPrepaidCardNets Prepaid / PBS gift card - Will be discontinued
    SB1GiftCardSparebank 1 / SB1 gift card
    SB1GiftCardCenterSparebank 1 / SB1 gift card center

    Wallet based payment methods



    SwishESwish E-Commerce
    SwishMSwish M-Commerce


    The following languages can be used in the hosted payment window:


    Was this helpful?

    What was your feeling about it?