Topical information about corporate customer software testing within OP Group. We recommend software testing in advance and also provide the means for testing.

When new data material formats and software versions are taken into use, we recommend that they be tested prior to the launch.

OP provides a dedicated customer test environment, the use of which is free of charge. The test environment can be used if the software provider’s or customer’s bank connection software supports the tested data contents and related feedback messages.

The use of the customer test environment requires that the customer has valid agreements with the bank concerning the services to be tested, for example, C2B payments, C2B agreement or e-invoice transfer agreement. The party transferring data contents to the bank through an online bank connection must have a valid Web Services agreement.

A separate testing certificate for the WS channel is necessary for the purpose of using the customer test environment. The production certificate does not work in the customer test environment. To retrieve the testing certificate,  a specific transfer key is needed, which is delivered to the customer once the relevant agreement is made. The certificate is retrieved by using the transfer key, as described in the WS channel implementation guidelines. The uploading of data contents to the test environment can start 24 hours after the retrieval of the certificate. Those customer identifiers, payment codes and payment accounts that are specified in the agreement shall be used in any data content uploaded to the test environment.

Testing is also possible in the XMLdation service

XMLdation can be used to validate the formal accuracy of data contents prior to the initiation of testing in the customer test environment. The use of the XMLdation validation tool does not require any agreements with OP. The service is subject to a fee and downloadable at:

The TUPAS authentication service is tested in a production-like environment with the same security requirements as are applicable to actual production, for example, the connection shall be encrypted whenever required in the production environment. Internet address: https://kultaraha.op.fi/cgi-bin/krcgi

Certificate request – test message

FORM data group

A01Y_VERS 0003
A01Y_RCVID Esittelymyyjä
A01Y_STAMP 20010125140015123456
A01Y_RETLINK https://+osoite/
A01Y_CANLINK https://+osoite/
A01Y_REJLINK https://+osoite/
A01Y_ALG 01
A01Y_MAC laskettu turvatarkiste

Return message

B02K_VERS 003
B02K_TIMESTMP 500vvvvkkpphhmmssxxxx
B02K_IDNBR tyhjä
B02K_STAMP kyselyn tietokenttä 7
B02K_CUSTNAME asiakas
B02K_ALG 01
B02K_CUSTID asiakastunnus
B02K_MAC vastauksen turvatarkiste

If desired, the service provider can test the functioning of our service by using the following input data:

Service provider: Esittelymyyjä (‘Demo salesperson’)
MAC key: Esittelykauppiaansalainentunnus (‘Demo merchant’s secret key’)

Use the following identifiers for the authentication of a private customer:

User ID: 123456
Password: 7890
Key code: any 4-digit number

Use the following identifiers for the authentication of a corporate customer:

User ID: 12345678
Password: 0987
Key code: any 4-digit number

Use the following identifiers if you want to test the request “y-tunnus+hetu” ("Business ID + personal ID") (A01Y_IDTYPE = 4Y or 5Y):

User ID: 1234567
Password: 8901
Key code: any 4-digit number

Invoicers can test their systems to verify the functioning of the MAC calculation and return links with the help of a Demo merchant (Esittelykauppias). During the testing, the invoicer can use the Demo merchant’s input data at the invoicer’s own test site.

The service’s URL address and other technical specifications are available at the Demo merchant test site, which also enables the user to learn more about the service. For a private customer, the demo identifier is 123456 and password 7890 (no key code is needed).

The demo merchant identifiers received from the bank are as follows:

Salesperson identifier = Esittelymyyjä (‘Demo salesperson’)
MAC key = Esittelykauppiaansalainen tunnus (‘Demo merchant’s secret key’)
MAC version = 1
Using the data from the Demo merchant’s test site, the MAC is calculated using the following values:


The MAC calculated from these values:


The following values are used for the MAC calculation:

<INPUT NAME="MAKSUTUNNUS" TYPE="hidden" VALUE="1997060417052135">
<INPUT NAME="MYYJA" TYPE="hidden" VALUE="Esittelymyyja">
<INPUT NAME=""SUMMA" TYPE="hidden" VALUE="30,00">

The MAC is calculated by using the following artificial function:

laske_MD5_tarkiste(VERSIO + MAKSUTUNNUS + MYYJA + SUMMA + VIITE + VALUUTTALAJI + TARKISTE-VERSIO + "Esittelykauppiaansalainentunnus")  

Testing of the payment function

If a company has a webstore for its products, the online payment button offers a convenient method for invoicing and collecting payments. This button payment system is the most popular e-payment method used in online trading.  It can be used by all online bank service users, and it is the easiest and safest way of paying for online purchases.

Testing of the payment enquiry function

The payment enquiry function is intended for companies with an OP online payment button in use. The payment enquiry function allows the company to check whether the payment has succeeded if there is any doubt about it, for example, if there are problems in data communications or the online connection fails. The payment enquiry function is in use as a default, and we save all payment data in the enquiry database.

Testing of the payment refund function

The payment refund function enables the company to return a payment that the customer has made by using the online payment button. The company can also pay a specific amount of money to the customer identified by the online bank service on the basis of the online payment button reference and payment code.