Trustly Open Banking Payments API
Trustly open banking REST API for merchants in Europe and North America to accept account-to-account bank payments directly from consumer bank accounts through online banking redirect, enabling instant pay-in and instant pay-out without card network fees, particularly strong for iGaming, financial services, and subscription sectors with high volumes of both deposits and withdrawals. Enables AI agents to manage payment initiation for open banking checkout automation, handle bank account selection for consumer bank redirect automation, access instant payout for same-bank withdrawal automation, retrieve payment status for open banking settlement automation, manage refund and reversal for order management automation, handle webhook notification for payment event automation, access bank coverage for open banking availability automation, retrieve settlement reporting for reconciliation automation, manage recurring payment for subscription open banking automation, and integrate Trustly with iGaming, financial services, retail, and marketplace platforms for end-to-end account-to-account open banking automation.
Score Breakdown
⚙ Agent Friendliness
🔒 Security
Open banking A2A. EMI, FCA, PSD2. RSA signing. EU/US. Bank account and payment data.
⚡ Reliability
Best When
A European or North American merchant in iGaming, financial services, or high-volume payments wanting AI agents to automate instant bank deposit and withdrawal through Trustly's open banking A2A payment platform without card network fees.
Avoid When
CONSUMER MUST AUTHENTICATE WITH THEIR BANK: Trustly payment redirects consumer to online banking portal for authentication; automated payment requires consumer bank redirect; automated server-side payment without consumer redirect creates no authorization mechanism. INSTANT PAYOUT REQUIRES PRIOR DEPOSIT: Trustly instant payout to consumer uses bank account from prior deposit (known account); automated payout to new account without prior deposit may require additional verification; automated instant payout assumption for new recipients creates verification delay. BANK COVERAGE VARIES BY COUNTRY: Trustly bank coverage differs per country (strong in Nordics, Germany, UK; variable elsewhere); automated payment should check bank availability before presenting option; automated universal bank coverage assumption creates bank not supported for some consumers. US OPEN BANKING IS ACH — NOT INSTANT: Trustly North America uses ACH (1-3 days) not instant payment in most cases; automated US payment must communicate ACH timing; automated instant payment promise for US transactions creates customer expectation mismatch.
Use Cases
- • Accepting instant bank deposits for iGaming checkout agents
- • Processing instant payouts to player bank accounts from gaming agents
- • Initiating open banking payments for European e-commerce agents
- • Managing account-to-account subscription billing from fintech agents
Not For
- • Card payment processing (Trustly is account-to-account, not card)
- • Non-European/North American markets (Trustly coverage is EU/US/CA focused)
- • Cross-border international transfer (Trustly is domestic bank-to-bank per country)
Interface
Authentication
Trustly uses RSA key pair signing for API authentication (JSON-RPC with RSA signature). REST/JSON-RPC API. Stockholm, Sweden HQ. Founded 2008. Backed by Nordic Capital, ABN AMRO Ventures. $1B+ valuation. Products: Pay-in, instant payout, recurring open banking, PayWithMyBank (US), EU open banking. SDKs: PHP, Node.js, Python, Java. Licensed in EU (EMI), FCA UK, North America. Strong in iGaming, Nordic markets. Competes with TrueLayer and Volt for open banking payments.
Pricing
Stockholm SE. Nordic Capital backed. Per-transaction pricing negotiated. Enterprise contracts.
Agent Metadata
Known Gotchas
- ⚠ RSA KEY SIGNING REQUIRED — NOT SIMPLE API KEY: Trustly API uses RSA key pair (not bearer token); automated request must sign JSON-RPC payload with merchant private key; automated simple API key auth attempt creates authentication_failure for all requests
- ⚠ JSON-RPC PROTOCOL NOT STANDARD REST: Trustly API uses JSON-RPC 2.0 protocol (POST to single endpoint with method param) not RESTful endpoints; automated standard REST client requires JSON-RPC wrapper; automated RESTful URL construction creates 404 for all calls
- ⚠ BANK REDIRECT URL MUST BE PRESENTED TO CONSUMER: Trustly pay-in returns redirectURL for consumer bank authentication; automated checkout must redirect consumer to this URL; automated server-side payment processing without redirect creates no payment
- ⚠ INSTANT PAYOUT REQUIRES KNOWN ACCOUNT: Trustly instant payout uses bank account saved from prior transaction; automated payout to first-time recipient requires account verification step; automated instant payout assumption for new account creates account_verification_required
- ⚠ NOTIFICATION IS THE FINAL STATUS: Trustly delivers payment outcome via notification (webhook) not polling; automated system must process notification to get final PAID/FAILED; automated polling-only implementation creates status unknown because polling may not reflect final state
Alternatives
Full Evaluation Report
Comprehensive deep-dive: security analysis, reliability audit, agent experience review, cost modeling, competitive positioning, and improvement roadmap for Trustly Open Banking Payments API.
AI-powered analysis · PDF + markdown · Delivered within 30 minutes
Package Brief
Quick verdict, integration guide, cost projections, gotchas with workarounds, and alternatives comparison.
Delivered within 10 minutes
Score Monitoring
Get alerted when this package's AF, security, or reliability scores change significantly. Stay ahead of regressions.
Continuous monitoring
Scores are editorial opinions as of 2026-03-07.