We can only offer limited support for users using our test account due to the amount of transactions made using that account. If you aren't an experienced developer or are unsure of your needs, contact merchant support before trying this.

Entry point: https://testapi.paynova.com
Merchant ID: 4999
API Password: secret

Basic Checkout Flow

The basic checkout flow consists of the three following steps:

  1. Create order
  2. Initialize payment
  3. Finalize payment

Order Management

Orders can be managed both via the API and with Paynova's merchant services tool.
Make sure you can do each of the order management services e.g a partial refund, full refund and an order update.

📘

Depending on which payment methods you want to offer there may be some restrictions on how many finalizations or refunds that may be performed, as well as the time-frame in which they are allowed to be performed.

Customer Profiles and Cards Management

Customer Profiles can be managed with the Paynova SDK's or the API services.

Basic testing can be done by

  1. Create an order and Initialize a payment and save a profile id and card (See [Initialize Payment](http://api.developers.paynova.com/docs/initialize-payment) and the [profilePaymentOption](http://api.developers.paynova.com/docs/profilepaymentoptions) parameter).
  2. Call [Get Customer Profile](http://api.developers.paynova.com/docs/get-customer-profile) and get the card id.
  3. Create a new order, initialize a payment and use the saved card.
  4. Remove the card by calling [Remove Customer Profile Card](http://api.developers.paynova.com/docs/remove-customer-profile-card)
  5. Call [Get Customer Profile](http://api.developers.paynova.com/docs/get-customer-profile) and verify that the card is removed.
  6. Remove the profile by calling [Remove Customer Profile](http://api.developers.paynova.com/docs/remove-customer-profile).
  7. Call [Get Customer Profile](http://api.developers.paynova.com/docs/get-customer-profile) and verify that the profile is deleted.

Event Hook Notifications

If you have EHN's enabled, make sure you test receiving them correctly.

Separate test instructions for EHN's are available in the Event hook notifications document.

Digests

To verify that the communication with Paynovas servers are correct you can use the digests available.

POST-redirect digests

Create an order, initialize a payment and make an approved payment. Check that the verification according to POST-Redirects/Verification is correct.

EHN digests

If you have EHN's enabled:
Create an order, initialize a payment and make an approved payment. Check that the verification according to event-hook-notifications#verifying is correct.

Logs

Paynova currently doesn't provide logs for the merchants, but all transactions can be viewed in the merchant support tool.

Payment Methods

Make sure you test all your available payment methods.

Below is a table of all payment methods and corresponding test possibilities.

Note: The testing procedures listed here only function within Paynova's test environment and cannot be used in the live/production environment.

Payment Method

Payments

Refunds

Comments

All Countries

Credit Cards

PayPal

We request that you set-up your own PayPal sandbox for testing.

Sweden

Nordea

SEB (Skandinaviska Enskilda Banken)

You must obtain your own credentials from SEB for their test environment.

SHB (Svenska Handelsbanken)

SHB does not have a test environment.

Swedbank

Swedbank does not have a test environment.

The Netherlands

iDEAL

iDEAL does not have a test environment.

Finland

Nordea

Aktia

Danske Bank

Danske Bank does not have a test environment.

Pohjola

Pohjola does not have a test environment.

Denmark

Nordea

EUROPE

Sofortüberweisung/Sofortbanking

Sofort does not have a separate test environment so we do not allow testing of this method by default to avoid accidental "live" payments from being made.


Test card payments

The following is a guide to simulating different card payments in Paynova's test environment.

Simulate Success/Decline scenarios

All combinations of card number, expiration date and CVC listed in the table below are considered declined. To simulate a success scenario, change one or several of the following parameters: expiration, cvc or amount.

Note that for Visa, our simulator is configured to allow several different decline scenarios; these are evaluated from top-to-bottom, using the first match.

Card Number

Expiration

CVC

3-D Secure

Amount

Result

Dynamic currency conversion

Visa

4111111111111111

January, any valid year

123

No

45.00, 42.00 or 36.00

Decline

Yes - If your merchant account was configured to use dynamic currency conversion (DCC). Authorizations with this card will need to be routed to a DCC configured routingIndicator set in the initialize payment step.

If you are not using DCC, this card will work just as any card.

4005550000000019

Any future date

123

No

Decline

No

Any valid card number

January, any valid year

123

No

11.11

Decline

No

4263879999019459

January, any valid year

123

No

Decline

No

4111111111111111

Any future date

111

No

Decline

No

4263879999019459

January, any valid year

123

No

Decline

No

Mastercard

No

5555555555554444

Any future date

111

No

Decline

Yes - If your merchant account was configured to use dynamic currency conversion (DCC). Authorizations with this card will need to be routed to a DCC configured routingIndicator set in the initialize payment step.

If you are not using DCC, this card will work just as any card.

5105105105105100

Any future date

111

No

Decline

No

Diners Club

No

30569309025904

Any future date

111

No

Decline

No

38520000023237

Any future date

111

No

Decline

No

American Express

No

378282246310005

Any future date

111

No

Decline

No

371449635398431

Any future date

111

No

Decline

No