Below you will find some of the frequently asked questions about Netaxept. If you can't find what you are looking for below, please contact our local customer support.


Q: What data do I need to send for a recurring transaction?
A: This depends on what type of recurring you are using, and what step in the process it is. If it is the initial call, and RecurringType R, you need to add RecurringType, RecurringFrequency and RecurringExpiryDate with the usual transactiondata. When using RecurringType S, you only need to send the RecurringType with the transactiondata.
To do the transactions after the initial one, you only need to add Panhash and RecurringType to the normal transaction data, which means no RecurringFrequency or RecurringExpiryDate.

Q: How can I see all the recurring transactions for one recurring agreement?
A: If you use your own interface to show the transactions, you should have a common identifier for these transactions (Ordernumber or TransactionReconRef, so you can see this on the settlement reports). If you use the Netaxept administration interface, you can look up one of the recurring transactions in the detailed view, and then click “History”. Then you will get a list of all the recurring transactions that has been done with this customer.

Q: I have recurring agreements with monthly transactions. What should I set the RecurringFrequency to?
A: The least days in the months are February with 28. You should set the RecurringFrequency to this number so you can do the transactions once a month, at a certain date.

Q: I have set the RecurringExpiryDate several years into the future, but I suddenly got error messages when I try to do these transactions that worked perfectly earlier. What’s wrong?
A: Even if the RecurringExpiryDate can be set far into the future in the Netaxept system, acquirer has a limit to how long they will accept the recurring transactions.  You should ask the acquirer how long an initial recurring transaction can be used. Also, if the card is renewed with new card data, the recurring information will be outdated and won’t be accepted. The customer has to redo the initial recurring transaction in either case.
Q: How do I receive the panhash?
A: In version 1.0 of the API, Panhash is returned after ProcessSetup. In the new API, you have to use the Query method to receive this information. This method can also be used in version 1.0 if you haven’t stored it already. Check the documentation about how a Query call is done.

Q: Is the panHash safe?
A: Yes. The panHash does, contrary to it's name, not contain any part of the pan (card number), nor is it a value calculated based on the pan. It is a randomly generated sequence, adhering to PCI standards.


Q: How do I see what transactions are what when it comes to the settlement reports from the acquirer?
A: Both Ordernumber and TransactionReconRef can be used for this. These two strings are sent back to the acquirer, and most put these numbers in the settlement reports.

Q: I would like a complete view over each transaction to our system. Are there any ways to receive this?
A: If you use the Query method, you will get the status and all information available for the transaction.

Q: Can I use Netaxept with iframes?

A: Netaxept is a concept based on setting up a financial transaction, then redirecting the end user to a Netaxept-hosted URL to process the payment operation, before redirecting back to a merchant-selected URL after the payment. To allow merchants to keep the look and feel of their respective websites throughout the buying process, we have developed a flexible template system for both mobile webapps, and for regular websites. This template system is flexible enough to handle any form of formatting that might be needed, making the terminal page virtually indistinguishable from any other page in your website.


We strongly encourage that you integrate with Netaxept through the templating system instead of with the use of iframes. Although we do not prohibit their use, we are aware of certain problems when integrating though iframes. Issues related to this use are not supported by Nets.


Q: What kind of browsers does Netaxept support?

A: Netaxept supports the most recent versions of all major browsers.


Q: How do I implement Netaxept payments in my mobile application?

A: The recommended, PCI-certifiable way to include the payment dialoge in your mobile application is to include the terminal through a WebView, while the rest of the normal API communication happens in the background as normal.


Q: Can I do any kind of performance testing before going live?
A: No, and for two reasons. One is that our test system is a separate entity, and although it is running the same code as in production, the hardware is fully separated from the production system – meaning that both the performance from our servers and the load they are experiencing is different from production. The second reason is that this wouldn’t be an end-to-end test since we in the test system are simulating the responses from the test system.

Both of these contribute to the fact that it’s no use to do performance testing in production. If you want to do end-to-end tests or test response times, these tests should be production tests before going live with your offering.

Errors and Exceptions:

Q: How do I know when a transaction fails or not? How should I handle exceptions?
A: For each method, if you get the ResponseCode ”OK”, the transaction has succeeded. If not, some sort of error has occurred. Whatever exceptions that occur, you should tell the customer that the transaction has failed and store the exception and the error message. Some exceptions could also be written out to the customer with your own message.

Q: I get the response ”Refused by issuer” during processSetup. What does this mean?
A: This error occurs because the customer’s bank refuses the transaction. The reasons for this problem can be many, and the customer should contact the bank to find out why the transaction won’t be allowed.

Q: “Security Error” shows on the terminal just after I press the pay button. Why does this happen?
A: This happens mostly if the setup of the merchant is wrong either at Nets or the acquirer. Contact Netaxept support if this happens, and tell them the error message as well as information such as transactionId and merchantId.