Invoice solutions

Enable customers to receive goods first and pay later without affecting your cashflow

 

This page outlines the basics of using "buy now pay later" payment methods via Netaxept and gives you instructions needed for a fluent implementation.

Use for the end-customer

If the customer decides to pay with an invoice, they are directed from the merchant’s site either to Netaxept payment window or to the website of the chosen invoice service provider. In the Netaxept payment window or service provider's site, the customer is guided through the payment process and after finishing it, the customer will be redirected to the redirectURL specified by the merchant in the Register call, with a proper response code. The invoice service provider sends the customer an invoice for the purchase as agreed and settles the payment to the merchant within the agreed time.

Activation

To be able to use invoice solutions in your webshop, you need to sign an agreement with each particular invoice service provider you want to use. After the chosen service provider has processed your agreement, they will provide you credentials which you need to enter to Netaxept Admin to activate the payment method in question. You will need to add one agreement for each of the combination of invoice, instalment or account that you want to have, per currency. The merchant is responsible for activating these payment methods in Netaxept Admin and ensuring that all information entered is correct.

 

• Log in to Netaxept Admin (test: https://test.epayment.nets.eu/admin or production: https://epayment.nets.eu/admin)
• Go to "Options" => "Agreement" tab.
• Choose the correct payment method from the drop down list and click "Add" button.
• Choose the correct currency and enter credentials. The number of credentials varies between different invoice providers, and the terminology varies as well.
• Save your changes by clicking "Add" button.

Performing API integration

Implement the technical API in accordance with the standard Netaxept's API instructions. Read more about API

Transaction flow

Start the payment process by sending the information required for the payment to Netaxept by means of the Register call. Compared to the regular card integration, there are some mandatory parameters that need to be sent along the Register call to Netaxept. See below for more information.

After the successful Register call, perform the Terminal call to send the customer either to the Netaxept payment window or directly to the invoice provider's site for the payment. If the invoice provider supports SCA, it is triggered in this phase. Regarding financial operations done after the Terminal phase, there are some differences depending on which invoice payment method has been used. Invoice payment methods don't support all financial operations, which eliminates a step in the standard payment process done via Netaxept. To make sure your setup doesn't try to run not allowed steps, we recommend you to implement the following:

• Use the "Payment method action list" parameter in the Register call to separate invoice from card and other payment methods in the checkout phase.
• Perform the Query call after the Terminal phase to see which payment method was used for the payment, and make the further action based on the payment status.
• Implement the supported financial operations per payment method as described in Payment methods

Mandatory parameters

Goods list

In the Register call, there is a Goods object, under the Order object, which is a mandatory object for all invoice payment methods implemented via Netaxept. The Goods object contains an array of Item objects, each containing a set of parameters. One Item object represents one product line / item. The full set of parameters is listed below. Boolean values are either "true" or "false". For float variables, use the "." character as delimiter, for example: 24 percent VAT is set as 24 or 24.00. Read more about these parameters

• ArticleNumber (string) (required)
• Title (string) (required)
• Amount (integer) (required)
• Quantity (integer) (required)
• Handling (boolean)
• Shipping (boolean)
• IsVatIncluded (boolean)
• Discount (float)
• VAT (float)

When working with REST interface, the format of the parameters needs special formatting. As the number of items is variable, you need to send a parameter "numberOfGoods" indicating how many product lines / items should be expected in the Goods list. Then, indexed from 1 up to "numberOfGoods", pass the parameters as amount_N, articleNumber_N etc. where "N" is the serial number of the item. Below you can find an example of this kind of REST call. In Web Services, numberOfGoods parameter is not needed.

Purchase 120 euros that contains two items with the following info:
1. 200 pencils, cost 0,50 euros each, incl. VAT 24%
2. Shipping, cost 20 euros, incl. VAT 0%
3. Payment method is selected in the merchant's webshop and Netaxept payment window is skipped

The Register call:
https://test.epayment.nets.eu/Netaxept/Register.aspx?merchantId=xxxxxxxx&token=xxxxxxxx&ordernumber=order852&amount=12000&currencycode=EUR&redirectUrl=http://www.test.fi&servicetype=B&language=en_GB&paymentMethodActionList=[{"PaymentMethod":"AfterPay"}]&numberOfGoods=2&amount_1=50&title_1=Pencil&quantity_1=200&articleNumber_1=1&VAT_1=24&IsVatIncluded_1=true&amount_2=2000&title_2=Shipping&quantity_2=1&articleNumber_2=2&VAT_2=0&IsVatIncluded_2=true&customerFirstName=Bill&customerLastName=Buyer&CustomerAddress1=Testadress&customerPostcode=00510&CustomerTown=Helsinki&customerCountry=FI

Customer information

Besides the Goods object, in most cases you need to provide customer information of the end-customer for invoice to be an option. The customer's country is mandatory for most of the invoice payment methods. It should follow ISO 3166-1 Alpha 2 code, for example: "NO", "SE", "DK", "FI".

There are also some customer information, like customer name, address, post code, town, email address, phone number and social security number that are required for some invoice payment methods. See more information from the table below. Customer information can be passed in the Register call or let customer to fill in the details in the Netaxept payment window. Read more about these parameters

Total sum of items

It should be noted that when accumulating the total sum of each item, it must match the sum specified for the transaction as a whole in the Amount / Order.Amount parameter in the Register call. In the example below, the one pizza (150 NOK) and two carrots (2 * 50 NOK) equals 250 NOK.

Order = new BBS.Order
{
Goods = new BBS.Item[]
{
new BBS.Item {
Amount = "5000",
Quantity = 2,
Title = "Carrots"
}, new BBS.Item {
Amount = "15000",
Quantity = 1,
Title = "Pizza"
}
},
CurrencyCode = "NOK",
Amount = "25000",
OrderNumber = "12345",
}, [...]

Process(Adjust) call:
https://test.epayment.nets.eu/Netaxept/Process.aspx?merchantId=xxxxxxxx&token=xxxxxxxx&transactionId=f48eecacdbbc45f7a82b8eec6544cdf8&transactionAmount=2000&numberOfGoods=1&amount_1=2000&title_1=ParkingFee&quantity_1=1&articleNumber_1=1&VAT=24&adjustmentType=positive&Operation=adjust&SubTransactionID=1822878