Integrating Trustly solutions allows your customers to pay or receive funds by signing in to their online banking interface directly within your website or application. This secure, direct-to-bank model reduces fraud risks and transaction costs while offering a familiar authentication experience for users.
Before you begin, you must select the integration model that best fits your business needs.
Trustly provides integration models for both online and physical environments.
For most online use cases, the Authorize and Capture (Deferred) model is the recommended integration.
The Instant Payments workflow (paymentType: 'Instant') is deprecated for new integrations. Trustly recommends using Trustly Pay for all use cases to ensure higher acceptance rates and risk optimization. If you are maintaining an existing integration, see Accept Instant Payments.
For physical casinos, Trustly provides a specialized workflow.
POST /qrcode/token). See Integrate Trustly Scan and Pay.If you need to send funds to a customer (gaming withdrawals, gig-economy payments), you must choose between the modern online banking flow or the manual account entry flow.
Use a data workflow if you need to verify information, tokenize accounts, or retrieve financial insights without processing a monetary transaction.
The following table lists the core concepts and components used across all Trustly integrations.
Regardless of which integration model you select, money moves through the banking network in a predictable lifecycle. Trustly provides visibility into this lifecycle through API status updates and event notifications.
When you collect funds (Capture) or send funds (Deposit), the transaction moves through the following states:
When you issue a Refund back to a user, the transaction follows a similar but distinct path:
Refunds progress through the same Authorized and Processed states as capture and deposit transactions before reaching Completed.