Skip to main content

Development Environment

An environment where production-like data is available and where you can test the implementation of individual endpoint calls. Any issues with these environments should be addressed via integrace_eshop@homecredit.cz or another specially agreed channel.

Prerequisites​

  • In order to call the test interface (the same applies to production), you must first obtain the username + password access data, which will then allow you to obtain an access token, without which it is not possible to call individual interface endpoints (more details in TD).
  • You should receive your access credentials from the responsible person at HC at one of the introductory meetings on the integration of our payment method.

Environment​

Available variants of the consumer API entity in the test environment:​

A) Sale without down payment (store ID 024242)

username: 024242tech, password: 024242tech

apiKey for the installment calculator in the javascript widget variant

  • CZ: calculator_test_key
  • SK: calculator_test_key

secret key for hashing [back communication to the e-shop] (https://github.com/homecreditcz/oneclick-api/wiki/Zabezpe%C4%8Den%C3%AD-zp%C4%9Btn%C3%A9-komunikace-partnersk%C3%A9mu-e%E2%80%90shopu "Securing return communication to the e-shop"):

  • CZ: !;8ez62oe{*,_
  • SK: %j:o)t:y/8)

B) Sale with down payment (store ID 024243)

username: 024243tech, password: 024243tech

apiKey for the installment calculator in the javascript widget

  • CZ: calculator_test_key_dp
  • SK: calculator_test_key_dp

secret key for hashing [back communication to the e-shop] (https://github.com/homecreditcz/oneclick-api/wiki/Zabezpe%C4%8Den%C3%AD-zp%C4%9Btn%C3%A9-komunikace-partnersk%C3%A9mu-e%E2%80%90shopu "Securing return communication to the e-shop"):

  • CZ: ..dw2{&q!.30
  • SK: wq%?ch.q%55r_

Payment calculator​

The following payment calculator options are available for testing purposes:

1. Partner's own solution​

The most developmentally demanding variant is the partner's own solution based on calculation endpoints (see TD). The advantage of this solution is, for example, the possibility of creating a calculator user interface entirely according to the partner's ideas and UX requirements.

Note: It is necessary to use the endpoint variant in the train environment.

2. Partial partner solution using a JavaScript widget​

The golden mean is a solution where the e-shop's own backend uses a JavaScript widget from Home Credit, which handles the frontend part, calculates suitable offers, and, based on the result, prepares the e-shop backend data for calling the endpoint to create a loan application.

3. External repayment calculator issued by Home Credit​

This is the only option for partners cooperating in the "Tipař" mode

The easiest way, where, apart from redirecting the client to the repayment calculation page via a simple link, no development is required

A sample URI for redirection may look like this, for example

Test queries​

o Even before implementation, the behavior of the interface can be tested quite easily using the Postman application, which is installed as a plug-in for the Chrome browser

o Complete sample requests that can be tested using the Postman application can be found at the end of this document (or in TD – however, relevant data must be used for these)

o The underlying data for sample requests, along with simple instructions, can also be found here

NOTE: For testing purposes, always use a financed purchase amount greater than 1000 (100,000 in minor units) for CZ, and greater than 40 (4000 in minor units) for SK

Working with applications in integration/test mode​

When testing in the integration phase, if you want to verify the entire process

  • from creating a request for financing of a client's purchase
  • through its approval and dispatch/delivery
  • to its successful completion

it is necessary to artificially simulate the client's behavior in the Home Credit front-end application (MyLoan). For this purpose, use the special Change application state resource, which is described in the technical documentation https://csoneclicknew.docs.apiary.io/#reference/testing-&-integration. This resource only works on the testing/integration environments specified in this document (or technical documentation).

Test run "approved"​

There is a special account for approval in the test environment (see above). The account function is activated by filling in the item last name = "Trener" when creating a request using the Create Application resource (in the request call POST https://apicz-test.homecredit.cz/verdun-train/financing/v1/applications, customer.lastName = Trener must be specified). Subsequently, whether you change the order status using the special Change state resource or fill out the application "manually," this application will always be approved. To sign the contract, you will ultimately need an OTP, which is 123456 for testing purposes.