Skip to content
Netaxept
    Operational status

    Link Payment

    This page outlines the basics of using Link Payment functionality in Netaxept.

    Prerequisites

    If you want to use Link Payment, you must sign an additional agreement with Netaxept. An eCommerce acquiring agreement is also required. Link Payment is considered a card-not-present solution where the merchant abides to the standard rules of eCommerce deliveries.

    Link Payment is mainly used for card payment transactions. However, most, but not all, payment methods available in Netaxept are supported also via Link Payment, as long as they are activated in your Netaxept admin portal.

    Before starting to create payment links, check that transaction timeout is disabled in Netaxept Admin’s "Options" => "Callback" tab. If transaction timeout functionality is in use, the link doesn't work and payment cannot be processed after the timeout value has exceeded.

    Overview

    If you don't have an integrated payment solution, or even if you don't a website at all, you can receive payments with Netaxept's Link Payment functionality. (You can use it in addition to your webshop integration as well).

    With Link Payment, your customers pay their purchases via payment links created by you.

    The link can be created in Netaxept Admin or via API if you have done an API integration towards Netaxept.

    In both cases you send the payment link to your customer, for example together with an offer, order confirmation or invoice by email, SMS or by other text media.

    When the customers click the link, a web browser will open and redirect them to the secure payment window offered by Netaxept. Here they will submit their payment method information to complete the payment.

    Link Payment works on desktop or laptop as well as on a tablet or on a mobile phone.

    Log in to your Netaxept Admin account, and go to "Help and Tools" => "Tools" and select "Link Payment". On the Link Payment page, fill in at least the mandatory fields. Amount, currency, order number and order description are shown to the customer in the payment window.

    • Amount: Required. The amount to be authorized or authorized and captured in the specified currency. Use a comma as a separator, for example €1,20 = 1 euro and 20 cents.
    • Currency: Required. The currency code for the transaction amount.
    • Order number: Required. A transaction identifier defined by the merchant. Nets recommends generating each transaction a unique order number since it helps you to keep track of the individual payment. However, if wanted the same order number can be used several times. Digits and letters are allowed except special characters, empty spaces and scandinavian letters like Æ Ø Å Ä Ö.
    • Order description: Optional. Free-format data content determined by the merchant and displayed to the customer on the payment window.
    • Transaction recon reference: Optional. A reference number allocated to the transaction by the merchant. The transaction reference number will be displayed in Netaxept Admin for the merchant and it will be returned to the merchant with the settlement if the chosen acquirer supports the return of the transaction-specific reference number. The transaction reference number can also be seen in the merchant's bank statement when direct bank payments are in question.
    • Language: Required. Language that is used on the payment window for the customer.
    • Auth / Sale: Required. Operation to be done automatically for the transaction after the customer has completed the payment window. According to card acquirers, payment must not be captured until the product or service has been delivered to the customer or there is certainty regarding its delivery. In between, you have the right to reserve the amount on the customer's account. It means that the operation SALE is only allowed if you sell services or products with immediate delivery. If you cannot deliver immediately, please don't use SALE operation, but instead use AUTH for reserving the money for the time being and later execute the capture in Netaxept Admin or via API.
      • Auth = Transaction will be only authorized
      • Sale = Transaction will be both authorized and captured
    • Customer information: Optional (required e.g. if direct banks via Paytrail). Customer information identifies the customer and is shown in Netaxept Admin for the merchant.

    After you have filled in all the needed information, create a payment link by clicking Create link. The payment link will be displayed at the top of the page in a green field. By clicking Copy you can copy the link to your computer’s clipboard for pasting it, for example, to an email that you are going to send to your customer.

    If you want to preview the payment window before sending the link, click Preview and the payment window will show as the customer will see it.

    Paylink

    Send the payment link by email, SMS or other channels. Remind the customer why you are sending a payment request. Also remember to inform your customer about return, refund and cancellation policies.

    User journey

    When your customers click the link, they are redirected to the payment window hosted by Netaxept. Here they enter their payment method information. You can customize this payment window with colours and merchant logo. This needs to be done before creating a link in the Netaxept Admin's "Options" section.

    If the payment fails and the customer informs you about the failure, it is recommended to create a new link and send it to the customer.

    Check incoming payments

    The transaction will be available in Netaxept Admin's "Transactions" tab as soon as the customer has completed the payment. For each transaction, you will see information about card type, date and time of when the transaction was completed by the customer, order number and amount you specified for the payment, and the status of the transaction.

    Captured payments are highlighted with a green bar and payments that are only authorized, are marked as grey bar.

    Depending on the status of the transaction, you can either capture or credit the money or cancel the authorization. To do this, click on a line in the table, to see the full details about the transaction, and then click the "Financial operations". Captures and credits can be done up to what's available for the transaction. Also, partial amounts can be captured and credited.

    Instead of using Netaxept Admin for generating payment links, you can also generate these links automatically through Netaxept API, as you would do in a regular webshop.

    The difference here is that instead of coming from a checkout page in a webshop, the customer would be directed to the payment window by clicking the link in an email or SMS sent by you. When Link Payment is used this way, API integration towards Netaxept is required.

    Implement the technical API in accordance with Netaxept's API instructions. Include either autoAuth=true or autoSale=true in the Register call, and send the Register call to Netaxept.

    The REST API messages must be sent to an address starting with:

    Dependent on the Register call's response, create the payment link for the customer. The link needs to include the Terminal call starting with:

    Also, the payment link needs to include your MerchantId provided by Nets and the unique TransactionId for each payment. You will receive the Transaction ID from the Register response received in the previous step.

    Below you can find an example of the link that is ready to be sent to the customer.

    Example Payment Link

    https://epayment.nets.eu/Terminal/default.aspx?merchantId=[MERCHANTID]&transactionId=[TRANSACTIONID]

    After you have sent the payment link to your customer and the customer has completed the payment in the payment window, you can further process the transaction either in Netaxept Admin, as described earlier, or via API.

    Was this helpful?

    What was your feeling about it?