Sign in
Sign up
Sign in
Sign up

Test Environment

  1. Home
  2. Test Environment

The Test Environment is a safe sandbox where you can explore and learn how our systems function without worrying about messing up your real account at OmnivaCheckout / Omniva.

Some notes:

  • We use bank-link emulators and test-cards here. There is no real money involved, so no worries. You can explore the whole process.
  • To test credit card dialog use one of the test cards below
  • The test version of the Merchant Portal has greenish header – to visually distinguish it from the real one
  • Payout processes are disabled in the test. Thus the balance of a Shop in Test Portal is always growing
  • Invoicing process is disabled, there are no invoices displayed in test environment
  • The identifiers and API keys are different in the Test and Live environments – so please be careful and do not mix them up

Test e-shops

for testing integration modules you could use the test-shops listed below  (test environment):

  • omnivacheckout.lv/test – banklinks and
    • E-shop ID = 43923dec-e723-40c2-8ead-78f62feed95f
    • API secret key = rN6zym97LgnvoLQ3ciPcxg9WtAaF2ospr9fLB5CDSY7SH7TmjW2XHllNZac3WBMy
    • API publishable key = 0Kx0CQO1aGaoqVJ58hHDPFdUtJdYwHyO

Testing bank-link and credit card payments

Test accounts and credentials

For most of the banklinks available in the emulator there is no authentication needed (login dialogs are skipped)

For the rest please use the credentials below:

EstoniaNordeaCode calculator: user ID = 111111   Response code = 9999
LatviaNordeaCode calculator: user ID = 111111   Response code = 9999
LatviaSEBnot functioning
LatviaCitadelenot functioning
LithuaniaNordeaCode card: user = 111111   code = 9999
FinlandNordeaCode Card: User ID=123456 Code=1234
FinlandDanskeuse your own user ID for testing. Payments will not be charged on your bank account
FinlandPohjola
FinlandÅlandsbanken
FinlandHandelsbanken credentials are displayed within the dialog

Test Credit Cards

There is a set of test cards you can use in our test environment (and Demo Shops). They do not function elsewhere.

When filling in the card data, use:

  • Expiry Date – any date in future
  • CVC – any 3 digits

Shortlist of test cards

  • 4012001037141112 – Visa – 3D Secure enabled
  • 4012001038443335 – Visa – 3D Secure NOT enabled
  • 5444870724493746 – MasterCard – 3D Secure NOT enabled
  • 5401030603708505
  • 5421590824439145

Cards to test specific use-cases (Visa)

  • 4012001037490014 – Valid 3-D Secure Message With Embedded Whitespace Characters (API error 1036: 3d secure field extraction from PaRes failed (946))
  • 4012001037141112 – Successful Authentication via 16-digit PAN (OK)
  • 4012001037167778 – Successful Merchant Attempt via 16-digit PAN (OK)
  • 4012001036275556 – No Response From Visa Directory Server (API error 1036: Authorization failed)
  • 4012001038443335 – Cardholder Not Participating (OK – fallback to regular payment)
  • 4012001038488884 – Unable to Verify Enrollment
  • 4012001036298889 – Invalid Response from Directory Server (API error 1036: Authorization failed)
  • 4012001036853337 – Invalid ACS Digital Signature (API error 1036: 3d secure field extraction from PaRes failed (946))
  • 4012001036983332 – Expired ACS Signing Certificate (API error 1036: 3d secure field extraction from PaRes failed (946))
  • 4012001037461114 – Authentication Failure (API error 1036:3d secure authentication failed (182))
  • 4012001037484447 – Authentication Not Available (API error 1036: 3d secure field extraction from PaRes failed(946))
  • 4012001037490006 – Invalid Payer Authentication Response (API error 1036:  3d secure field extraction from PaRes failed (946))
    Sign in
    Sign up