Products

Trustly's SDKs and APIs provide various tools and workflows for building Data and Payments integrations. Whatever your application's needs, Trustly can be used to create a powerful Online Banking integration.

Data

Gain financial insights on consumers in order to inform business decisions and streamline Know-Your-Customer processes.

Account Data Retrieval	Account Routing Validation	Tokenization
Retrieve account information for data insights or payment initiation. After a user signs into their Online Banking account, retrieve account information for further data insights or payment initiation purposes.	After a user signs into their Online Banking account, validate account routing information for further data insights or payment initiation purposes.	Store highly sensitive information and ensure the security of consumer financial data. Meet the NACHA requirements for account tokenization and verification—store highly sensitive information via Trustly’s patent-pending tokenization technology.

Payments

Enable efficiency and expediency at the checkout by adding any of Trustly’s payment methods to your checkout page.

Disbursements	Guaranteed & Non-Guaranteed	Instant Payouts	Recurring Payments
Use authenticated bank information to implement one-time or consecutive payouts. Authorize consumer bank information and pass the information to Trustly via Establish a Transaction. To initiate a payout or disbursement, pass the transactionid to the Deposit API to disburse funds into the consumer’s bank account.	Mitigate risk and protect revenue with flexible payment options—Trustly absorbs the upfront cost of transactions in real-time, allowing merchants to accept payments without fear of chargebacks.	Initiate real-time payouts using Trustly's Deposit API. Trustly Instant Payouts uses the Trustly Open Banking Payments flow to authorize their bank. After authorization, the transactionid and the Deposit Transaction operation are used to deposit funds in the consumer's bank account in real-time—enhancing satisfaction and building loyalty.	Pull funds at regular intervals after one-time user consent. Optimize operations and manage churn with recurring payments—consumers validate account information one-time and funds are pulled at regular intervals.

Payment Types

Name	ID	Description
Deferred	2	This is a 2-step operation. First, the customer authorizes the payment and then the capture service must be called one or more times to execute the debits. A capture is actually an API call to PayWithMyBank done by the merchant. The sum of the amounts of all captures associated to a single transaction must be less than or equal to the total amount authorized by the customer in the first step. It’s represented in the system by 1 + 1 or more records: 1st: Payment type = "Deferred". Transaction type = "Authorize". 2nd and forward: Payment type = "Deferred". Transaction type = "Capture".
Recurring	3	Represents a recurring payment. It’s similar to deferred, but associated to a payment agreement between consumer and merchant that defines the amount of each capture, how many times and when the capture API can be called. Thus, the customer first authorizes the payment and then many captures are executed – one for each recurring instance. This is frequently used for monthly payments, such as rents. In this case, the captures can be automatically generated by us or manually executed by the merchant via API call, depending on how it is configured. It’s represented in the system by 1 + many records: 1st: Payment type = "Recurring". Transaction type = "Authorize". 2nd and forward: Payment type = "Recurring". Transaction type = "Capture".
Disbursement	4	It’s also similar to deferred, but in this case the merchant transfers money to the customer. In the first step the customer informs the account on which he wants to receive the money. This is the authorization step. Then a deposit operation is called to effectively transfer the money. A common use case is insurance payment. It’s represented in the system by two records: 1st: Payment type = "Disbursement". Transaction type = "Authorize". 2nd: Payment type = "Disbursement". Transaction type = "Deposit".
Verification	5	Service used to verify the customer’s bank account. The payment is done outside of PayWithMyBank. It’s represented in the system by a single record: Payment type = "Verification". Transaction type = "Authorize".
Retrieval	6	Service that enables the merchant to retrieve specific information from an end-user’s US bank account, so the payment can be done outside of PayWithMyBank. It’s represented in the system by a single record: Payment type = "Retrieval". Transaction type = "Authorize".