Trustly
Trustly is a fast, secure, and user-friendly online payment solution that enables consumers to make direct bank transfers for goods and services without using a card or app. Trustly allows users to pay directly from their bank accounts in real time, no registration required, and it's available in all major markets in Europe. Learn more about Trustly.
PPRO does not currently support merchants offering money transfer services (including remittance houses), e-wallets or prepaid cards.
Payment method properties
Markets (consumer) | AT CZ DE DK EE ES FI GB LT LV NL NO SE |
Processing currencies | CZK DKK EUR GBP NOK SEK |
Consumer currencies | CZK DKK EUR GBP NOK SEK |
Authentication methods | REDIRECT |
Authentication timeout | 10 minutes of inactivity |
Minimum payment amount | 0.01 EUR (or equivalent) |
Maximum payment amount | None |
Payment instrument | BANK_ACCOUNT |
Recurring payments | No |
Separate captures | No |
Refund | Full - Partial - Multiple |
Refund validity | 365 days |
Disputes | No |
Settlement risk | Yes. Can be avoided by configuring Trustly to use the Authorization Async flow. |
Make a Trustly payment
Trustly payments follow our standardized REDIRECT
payment flow. However, we recommend including all relevant settings for any authentication methods you support.
To make a Trustly payment, you'll need to provide the following data at minimum when calling our /v1/payment-charges endpoint:
Field | Description |
---|---|
|
|
| The amount to be paid in the smallest units of the currency used. |
|
|
| Full name of the consumer. |
| The email of the consumer. |
| The country of residence of the consumer. |
| ID, username, hash or anything uniquely identifying the consumer. Preferably the same ID/username as used in the merchant’s own system. |
authenticationSettings: REDIRECT
| Specify the URL to which the consumer should be redirected after completing the payment. This is required for the |
GuidanceTo improve the consumer experience and payment traceability, consider including the following fields. See the API Reference for full details.
Fields Description paymentDescriptor
Text to show on the consumers bank statement after Trustly’s own 10 digit reference (which always will be displayed first).
Request
POST /v1/payment-charges
{
"paymentMethod": "TRUSTLY",
"amount": {
"value": 1000,
"currency": "EUR"
},
"consumer": {
"country": "DE",
"name": "John Smith",
"email": "[email protected]",
"merchantConsumerReference": "consumer-ref-3"
},
"authenticationSettings": [
{
"type": "REDIRECT",
"settings": {
"returnUrl": "https://www.webshop.com/order-results-page"
}
}
]
}
Response
You'll receive our standard payment charge response with the available authentication methods:
{
"id": "charge_k0JhIhoQpxaVDobnm7ggL",
"paymentMethod": "TRUSTLY",
"paymentMedium": "ECOMMERCE",
"scheduleType": "UNSCHEDULED",
"instrumentId": "instr_9HeiXYhPOuo8Ext0k8kRH",
"currency": "EUR",
"country": "DE",
"status": "AUTHENTICATION_PENDING",
"consumer": {
"name": "John Smith",
"country": "DE",
"email": "[email protected]",
"merchantConsumerReference": "consumer-ref-3",
},
"authenticationMethods": [
{
"details": {
"requestUrl": "https://redirection-target.ppro.com",
"requestMethod": "GET"
},
"type": "REDIRECT"
}
],
"authorizations": [
{
"id": "authz_ZVxqyEjacRagwrOvwEhBt",
"amount": 1,
"status": "AUTHENTICATION_PENDING",
"merchantPaymentChargeReference": "test-id-3",
"createdAt": "2025-07-17T08:06:01.736Z",
"updatedAt": "2025-07-17T08:06:01.736Z"
}
],
"captures": [],
"refunds": [],
"discards": [],
"voids": [],
"createdAt": "2025-07-17T08:06:01.422Z",
"updatedAt": "2025-07-17T08:06:01.736Z",
"_links": {
"authorizations": {
"href": "/v1/payment-charges/charge_k0JhIhoQpxaVDobnm7ggL/authorizations"
},
"captures": {
"href": "/v1/payment-charges/charge_k0JhIhoQpxaVDobnm7ggL/captures"
},
"refunds": {
"href": "/v1/payment-charges/charge_k0JhIhoQpxaVDobnm7ggL/refunds"
},
"discards": {
"href": "/v1/payment-charges/charge_k0JhIhoQpxaVDobnm7ggL/discards"
},
"voids": {
"href": "/v1/payment-charges/charge_k0JhIhoQpxaVDobnm7ggL/voids"
}
}
}
Pick the desired authentication method
REDIRECT
- Redirect your consumer to the returned
$.authenticationMethods[?(@.type == "REDIRECT")].details.requestUrl
.
For example, with the value ofhttps://redirection-target.ppro.com/
using the returned$.authenticationMethods[?(@.type == "REDIRECT")].details.requestMethod
HTTP method. - The consumer will be presented with the reference number and instructions to complete the payment.
Handling the payment result
REDIRECT
- After the consumer completes the payment, they are redirected to the
returnUrl
specified in the payment charge creation request. - Upon redirect back to your site, retrieve the latest payment status by performing a GET /v1/payment-charges/{paymentChargeId}. Use the returned
status
field to determine and display the final payment outcome to the consumer. - Additionally, webhooks are triggered to notify you of the payment result. This ensures you receive the outcome even if the consumer closes their browser or fails to return to your website.
Payment instrument
An instrument of type BANK_ACCOUNT
will be created for Trustly payments where the consumers bank account details can be returned.
Request
GET /v1/payment-instruments/{instrument-id}
Response
{
"id": "instr_9HeiXYhPOuo8Ext0k8kRH",
"details": {
"holderName": "John Smith",
"iban": "DE81753400900062568848",
"bankCode": "75340090"
},
"type": "BANK_ACCOUNT"
}
Sandbox testing
The Trustly sandbox works the same way as the live environment, except no real money or banks are used when performing payments. Use any 8 digit Login ID and the dummy OTPs displayed on screen to complete the payment.
Updated 3 days ago