Skip to content

    Service usage specification

    Overview

    The services published by the e-commerce payment gateway support the HTTP protocol with channel encryption and use the NVP format for the request and XML format for the response.

    Specifications for API calls

    The technical details for sending messages are described in the table below:

    ProtocolHTTPS
    MethodPOST
    Content-Typeapplication/x-www-form-urlencoded
    Production urlhttps://xpay.nexigroup.com/monetaweb/payment/2/xml
    Test urlhttps://stg-ta.nexigroup.com/monetaweb/payment/2/xml

    The only protocol supported is TLSv1.2. Below are the ciphers:

    • TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256
    • TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384
    • TLS_ECDHE_RSA_WITH_CHACHA20_POLY1305_SHA256

    The encoding used for the individual characters must be ISO 8859-1.

    Specifications for the response

    Responses to calls to synchronous services use XML format.

    Within the paragraph of each payment protocol, examples are shown with the correct path.

    Specifications for outcome notification

    Payment notifications for asynchronous services can only be made on ports 443 or 8443.

    Below are the IP addresses of the Gateway from which notifications are sent:

    DomainIP addresses
    stg-ta.nexigroup.com
    • 151.99.182.114
    • 151.99.182.115
    • 151.99.182.120
    xpay.nexigroup.com
    • 151.99.182.114
    • 151.99.182.115
    • 151.99.182.120

    Was this helpful?

    What was your feeling about it?