Testing

Novalnet recommends testing your shop with sample data before moving the shop online. The sample data includes credit card data and other information to test your integration by performing a trial checkout process. You can use this data to trigger different flows in your integration and ensure they are handled accordingly.

If you are not a Novalnet merchant, you can use the sample Merchant API credentials given below to test transactions. You can try all the payment methods with their test data and then enable the payment methods before going live.

Once you have created the merchant account with Novalnet, you will receive your merchant credentials to your registered email address from sales@novalnet.de. The email will also contain the Novalnet service contract and supporting documents. You can also use your merchant account to perform the tests effectively.

How to execute a TEST transaction?

In various cases, Novalnet will mark your transaction as a TEST transaction. Instances where Novalnet will evaluate as test transactions are,

  • After you create an account with Novalnet, your merchant account will be in TEST mode initially. So, you can proceed with the testing using your merchant account credentials.
  • You can initiate the transaction in TEST MODE even after you have moved Novalnet's account from TEST to LIVE by sending the parameter transaction.test_mode as 1 (or) by using any TEST payment details.

Shortly after midnight, all test transactions and the subscriptions created by test transactions will be deactivated automatically and will not be available in our system. Hence you can not execute a payment reference call or a refund call for an original transaction which ran on test mode a day before or on any previous days.

Testing in a Live environment

By default, you can also use Novalnet‘s test credentials in the live environment to execute tests in a live environment. Whenever a transaction is executed in test mode, with test cards, or with test user data, the transaction will run in test_mode at Novalnet. Therefore, you will always receive the parameter transaction.test_mode as 1 in the Novalnet response.

By evaluating the transaction.test_mode parameter value in the Novalnet response, your system can identify if this transaction ran on TEST mode (test cards, test user data, etc.) or not! Upon that, your system can handle the status of the transaction internally.

Please note if you want to block test transactions (with test payment credentials, test user credentials, test_mode=1) on Live mode. You can simply configure it in the Novalnet Adminportal under Account -> Global Configuration (refer to screenshot) to reject all test transactions in Live mode.

Rejecting Test data in Live environment

By default, the merchant will be able to use this option to reject orders while using Novalnet's test credentials for the transactions that are executed in LIVE mode.

Please note if you want to allow test transactions (with test payment credentials, test user credentials) on Live mode. You can simply configure it in the Novalnet Adminportal under Account -> Global Configuration to allow all test transactions in Live mode.

Merchant API credentials

The below table contains the test merchant data for API calls. Please use only these details (Product Activation key, Payment Access key, Tariff, etc.) for successful API calls.

Product Activation Key
7ibc7ob5|tuJEH3gNbeWJfIHah||nbobljbnmdli0poys|doU3HJVoym7MQ44qf7cpn7pc
Payment Access Key
a87ff679a2f3e71d9181a67b7542122c
Client Key
88fcbbceb1948c8ae106c3fe2ccffc12
Tariff ID
10004
Predefined Subscription Tariff ID
10005
Dynamic Subscription Tariff ID
10006

To get your Merchant API credentials, please log in to Novalnet Admin Portal and navigate to the path Projects -> [Select the project] -> API credentials.

Customer Data

For customer details, please use the below sample data for successful user validation.

First name
Max
Last name
Mustermann
E-mail
test@novalnet.de

Address Data

Use the below data in your checkout while testing the Novalnet payment in a test environment.

Guaranteed Payment-B2C

For the guaranteed payment method tests, please use either Date of Birth or Email Address in the user details below to simulate the flows for B2C customers:

  • Accepted - Transaction approved by the guarantor
  • Pending - Transaction is under manual review by the guarantor, usually takes up to 24 hours to reach a final decision in production.
  • Declined - Transaction declined by the guarantor due to risks

Guaranteed Payment-B2B

For the guaranteed payment method tests, please use either Company Name or Email Address in the user details below to simulate the flows for B2B customers.

Payment Data

Credit/Debit Cards

When you execute test transactions using a card payment, please use the below card data. 3D-Secure and Non-3D Secure card details are furnished in the table below. To test with wrong or false data, use the card details under Decline. After using each of the card details, kindly check the status description is the same as below.

Card holder
Max Mustermann
Expiry date
Any valid future date, such as (01/31)
CVC
Any 3 digit CVC, such as 123 (4 digits for American Express cards)

When performing test transactions using token, please use the token provided below.

Failure

Token Status Description
VDTRVB20u-VR00aXT24yV-14o22wR22w10k22wX20uZBR14o16q18sXT14o14841
509007 - Card expired
VDTRVB20u-VR00aXT24yV-14o22wR22w10k22wX20uZB00a22w16q20uV22w20u1
406012 - Insufficient funds or credit limit exceeded

If asked for the Purchase Authentication code, please enter 1234 to complete Purchase Authentication, as displayed in the authentication screen.

To generate failure bookings for the affiliate, please pass the corresponding affiliate share with 120 EUR for the Marketplace transactions.

Direct Debit SEPA

When you execute test transactions using Direct Debit SEPA, please use the below account details for various countries.

Account Holder
Max Mustermann
Country
IBAN
DE24300209002411761956
BIC
CMCIDEDDXXX

Direct Debit ACH

When you execute test transactions using Direct Debit ACH, please use the below account details for a successful transaction.

Account Holder
Max Mustermann
Account Number
123456789
Routing Number (ABA)
031200730

PayPal

When you execute a test transaction with PayPal payment type, use the below sample login for a successful transaction.

Email Address
pb-buyer@novalnet.de
Password
novalnet123

iDEAL | Wero

When you execute a test transaction using iDEAL | Wero, select the following bank name on the iDEAL | Wero payment page. After selecting the bank, proceed to simulate the test transaction as required.

Bank name
TESTNL2A

eps

To perform a test transaction using EPS, follow the steps below:

  1. On the payment page, select "PSA Bank Group" as the bank.
  2. Log in using the test credentials:
    3. Username
    1006044
    Password
    PPRO1234$$
  3. After login, the test IBAN and test BIC will automatically populate in their respective fields. If they do not appear, enter them manually:
    4. IBAN
    AT058900000001100541
    BIC
    STZZATWWXXX
  4. On the same page down below, click REQUEST TAN.
    • The generated TAN number will appear on the left.
    • A text box will appear on the right for entering the TAN number.
  5. Enter the generated TAN number into the TAN field, and then click SEND TAN to complete the test transaction.

To generate failure transaction, please enter transaction amount over 500 EUR.

Przelewy24

Choose any of the banks from the Przelewy24 page. After the bank selection, please log in (if required) using the below credentials and simulate the TEST transaction.

Email Address
sandbox
Password
sandbox

PostFinance

When you execute a test transaction using PostFinance (Card or E-Finance), use the below details for a successful transaction.

Bancontact

When you execute a test transaction using Bancontact, use the below Bancontact details for a successful transaction.

Card holder
Max Mustermann
Card Number
6703 4444 4444 4449
Expiry date
12/2028
CVC
123

Apple Pay

While executing test transactions using apple pay, you need to set up your Apple Pay sandbox account for the development and testing in your Apple Developer account and perform the following steps:

  • Sign in to Apple Developer account.
  • Click on the link Users and Access, under App Store Connect and then navigate to the Sandbox Testers tab.
  • Click the "+" icon to set up a new test account. After filling the form, and click Create.
  • Sign out of your Apple ID on all testing devices if logged in. And then log in with the new test credentials.
  • Navigate to Settings -> Wallet & Apple Pay
  • Tap Add Credit or Debit Card and add the test Card data. You can find the test Card numbers under "Test Cards for Apps and the Web" Apple Pay Sandbox Guide.

Google Pay

You can follow the test card procedures to proceed with the demo transaction. Once the test setup is done, click the Google Pay payment button and choose the payment card listed in the payment sheet.

Trustly

Test your payment system using the data provided in Trustly. This testing platform contains a complete set of data for testing purposes. While placing the test order, you will be prompted for a one-time passcode; use the code provided in the form.

Alipay / Wechat Pay / Payconiq

When you execute a test transaction with Alipay, WeChat pay or Payconiq, use the below details for a successful transaction.

Username
test
Password
1234
Payment Methods
Select any one from the list

Online bank transfer

Choose any of the banks from the Online bank transfer page. After the bank selection, please log in (if required) using the below credentials and simulate the TEST transaction.

While placing the test order, you will be prompted for a one-time passcode; use the code provided on the form and choose any available options for bank accounts for a successful transaction.

Blik

When you execute a test transaction with Blik, follow the steps below for a successful transaction.

  1. If the system prompts for a BLIK code, enter the code: 999016
  2. After entering the code, if a message asks you to complete the payment via the mobile app:
    • Stay on the page for 2-5 seconds without any further action.
    • The simulation will automatically complete after the brief pause.

MB Way

When you execute a test transaction with MB Way, use the below details for a successful transaction.

Country Code
351 (Select any one from the list)
Mobile Number
915245709

KakaoPay

  • To successfully test KakaoPay payments, you will need the KakaoTalk app.
  • Download the KakaoTalk app: Kakao Pay is integrated with the KakaoTalk app, so you'll need to have KakaoTalk installed on your mobile device. You can download it from the App Store (iOS) or Google Play Store (Android).
  • Create or sign up for a Kakao account: Launch the KakaoTalk app and either create a new Kakao account or sign in with your existing account.
  • Link your bank or credit card: To use Kakao Pay, you'll need to link a valid bank account or credit card to your Kakao account. Follow the instructions in the KakaoTalk app to link your preferred payment method.
  • Testing KakaoPay: Please note that there is no special testing data associated with KakaoPay, you will need to make real purchases of smaller amounts to test. To test, you will need to scan the QR code displayed on the KakaoPay payment page using your KakaoTalk app. You can either use biometric authentication or enter your 6-digit PIN for a successful transaction. Once the test has been completed, you can refund the successful KakaoPay transactions.
  • To successfully test payments with Naver Pay, you will need the Naver app.
  • Download the Naver app: Naver Pay is integrated into the Naver app, so you'll need to have the Naver app installed on your mobile device. You can download it from the App Store (iOS) or the Google Play Store (Android).
  • Create or log in to a Naver account: Launch the Naver app and either create a new Naver account or sign in with your existing account.
  • Set up Naver Pay: Within the Naver app, find the Naver Pay option. It can be found in the main menu or as a separate tab. Follow the instructions to create your Naver Pay account.
  • Link it to your bank account or credit card: To try Naver Pay, you'll need to link a valid bank account or credit card to your Naver Pay account. Follow the on-screen instructions to link your preferred payment method.
  • Testing Naver Pay: Please note that there is no special testing data associated with Naver Pay, you will need to make real purchases of smaller amounts to test. To test, you will need to complete authentication in the Naver app. Once testing is complete, you can refund successful Naver Pay transactions.

Samsung Pay

  • Check device compatibility: Samsung Pay is available on select Samsung devices. Make sure your device is compatible with Samsung Pay by checking the official Samsung Pay website or the device specifications.
  • Install Samsung Pay: If Samsung Pay is not pre-installed on your device, you can download it from the Galaxy Store (for Samsung devices) or the Google Play Store (for non-Samsung devices).
  • Set up Samsung Pay: Launch the Samsung Pay app and follow the on-screen instructions to set up your Samsung Pay account.
  • Add payment methods: Within Samsung Pay, you can add your credit or debit cards by either manually entering the card details or using the device's camera to capture the card details.
  • Verify your card: Depending on your bank's verification process, you may need to verify your card using a one-time password (OTP), a phone call, or other methods provided by your bank.
  • Testing Samsung Pay: Once your payment methods are added and verified, you can test Samsung Pay by making payments at checkout by clicking the Samsung Pay button. Please note that there are no special test card details associated with Samsung Pay, you will need to make real purchases of smaller amounts to test. Once the testing is complete, you will be able to refund the successful Samsung Pay transactions.

Even if you are processing the transaction in the TEST environment, please use the above account details (no other personal account) to avoid processing an actual transaction.

Related Topics