Technical implementation FAQ

Find answers to the most common questions about integrating Paytrail with your e-commerce platform. This FAQ offers practical guidance and examples to help you set up, test, and manage Paytrail’s payment service smoothly and without errors.

You’ll find information about compatible platforms and partner plugins, testing before signing an agreement, key integration steps and test credentials, recommended request fields, processing refunds through the API, retrieving settlement reports, handling marketplace split payouts with Shop-in-Shop, and sending payment links from the Merchant panel or via Paylink.

What platforms is Paytrail compatible with and where can I get the plugins for them?

Paytrail is compatible with most major e-commerce platforms. The plugins and modules for these platforms are developed and maintained by our partners. See the list of compatible platforms and plugins.

Can we test the payment service before signing an agreement?

Yes. You can test the payment flow and key features in a test environment before you sign. See instructions on how to test the payment service.

How do we integrate Paytrail in our platform?

Integrating Paytrail’s payment interface into an online store is generally easy and quick. Provide the following info to your team or technical partner so they can integrate Paytrail's service:  

  • Typically, the integration can be completed within a few working days. Our technical customer service is available to assist as you do the integration: tech@paytrail.com
  • See our integration documentation.
  • Once you have finished the integration, you can test payments using test credentials as they work the same as the live credentials.
What features of the service we implemented?

Choose the features that support your business goals. Sending comprehensive data unlocks more capabilities. Below are some points to consider:

  • In the implementation, you can partially define what information about the payer and products is sent to Paytrail from the online business. The imported data generally affects the available features, so we recommend sending comprehensive data. See all the possible fields that can be sent with in the payment.
  • Process refunds in your own system via API and not through Paytrail's Merchant panel. See our refunds documentation
  • You can retrieve settlement data via the interface from Paytrail's system without logging in to the Merchant panel. When retrieving a settlement report with the settlement ID, you must provide the requestType, i.e. what file format the report should be (json or csv), and the Callbackurl where the report is sent once completed.
Can one payment be split and paid out to multiple companies or accounts?

Shop-in-shop makes multi-party payment distribution seamless and automatic. The main idea is simple: the platform owner or parent company manages the website/platform, while the connected businesses automatically receive their share of each payment.

Paytrail pays out the money directly to the company that sold the products/services. The admin is not responsible for the payments and doesn't need a payment service provider license from the Financial Supervisory Authority. For consumers, Shop-in-Shop makes it possible to buy from multiple companies with a single payment.

Explore Shop-in-Shop or contact our sales team: sales@paytrail.com

How can I create or send a payment link to a customer?

There are two ways to send a payment link in Paytrail's service:

  1. Send a payment link to the customer from the Merchant panel, see instructions on creating a payment link.
  2. Send a payment link using the Paylink service. Customers can pay with the payment methods active for your account (for example, online banks or cards). Once the customer has paid, you can deliver the products. Paylink includes its own portal for sending payment links, and Paytrail’s payment methods can be activated within Paylink. Explore Paylink or try the demo.

Need help?

Technical support
✉️ tech@paytrail.com

Was this article helpful?
1 out of 3 found this helpful