How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

PayWithMyBank (Trustly) payments API

The payments API from PayWithMyBank (Trustly) — 2 operation(s) for payments.

PayWithMyBank (Trustly) payments API is one of 11 APIs that PayWithMyBank (Trustly) publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Payments. The published artifact set on APIs.io includes an OpenAPI specification.

This API exposes 2 operations across 2 paths, and defines 27 schemas. It is described by OpenAPI 3.1.0, at version 1.0.0.

Requests are made against a single base URL, https://sandbox.trustly.one/api/v1.

2 operations 2 paths 27 schemas 2 GET

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.1.0
API Version
1.0.0
Base URL
https://api.trustly.one/api/v1
Authentication
HTTP Basic
Resource Areas
1

Authentication & Security 1

PayWithMyBank (Trustly) payments API declares 1 security scheme for authenticating requests. It accepts HTTP basic authentication (HTTPBasic).

Paths & Operations 2

Across 2 paths, the API surfaces 2 operations — 2 GET. Each is listed below with its method, path, parameters, and response codes.

payments 2
GET
/payments
List payments
list-payments 25 params → 200
GET
/payments/{paymentId}
Retrieve payment
get-payments 2 params → 200

Schemas 27

The contract defines 27 schemas that model the data the API accepts and returns. The most detailed are Payment (34 properties), Customer (21 properties), Account (15 properties), Recurrence (10 properties). Each schema is shown below with its type and property counts.

Verification
object
3 properties
CustomerCustomData
object
Object for sending merchant-specific custom data.
PaymentSystem
string
Financial Institution Account Type: -1: None 1: PayWithMyBank 2: TrustlyAB
PaymentMerchant
object
2 properties
Address
object
Valid mailing or billing address associated with the customer
6 properties 1 required
DriverLicense
object
2 properties 2 required
PaymentProviderSubType
string
Financial Institution Account Type: 1000: Online Banking 2000: Manual Entry 2001: Manual Entry with Challenge Deposit
FinancialInstitutionAccountVerificationScore
string
Verification Score: 0: Invalid input. The account or routing number are invalid. (Verified Mapping = false) 1: There is a strong indication that the account is…
Customer
object
The Trustly customer object, containing identification details and contact information.
21 properties 4 required
VerificationStatus
string
Verification Status: 1: Automatic - Payment verification followed Trustly internal rules. 2: ToVerify - Payment transaction is held (status = OnHold) for furth…
PaymentCurrency
string
3-letter ISO Currency Code. Currently only USD is supported.
AccountCountry
string
2-character ISO code of the country for the bank account that was selected. Currently only the US, CA, UK, DE, and AU are supported.
Payments_list-payments_Response_200
object
3 properties 3 required
PaymentProviderSubtype
string
Payment Provider Subtype: 1000: EasyOnline 2000: MEC 2001: MCD
PaymentProvider
object
Details of the Financial institution
9 properties 1 required
VerificationMode
string
Verification Mode: 1: VerifiedByMerchant 2: ApprovedByMerchant 3: VerifiedByTrustly 4: AmountAuthorizedByMerchant
PaymentCountry
string
2-character ISO code of the country for the bank account that was selected. Currently only the US, CA, UK, DE, and AU are supported.
PaymentProviderCountry
string
2-letter ISO country code of the financial institution
FinancialInstitutionAccountVerification
object
8 properties 4 required
FinancialInstitutionAccountVerificationType
string
Verification Type: 1: Manual - The account was verified with manual account verification. For example, Manual Electronic Check and Micro Challenge Deposit. 2:…
RecurrenceFrequencyUnitType
string
Frequency Unit Type
PaymentAuth
object
3 properties
Recurrence
object
Recurring payment options
10 properties
PaymentPaymentType
string
Financial Institution Account Type: 1: Instant - Instant payment. The debit instruction is automatically initiated with that day's batch after consumer authori…
FinancialInstitutionAccountVerificationThirdPartyScore
string
Verification Third-Party Score: 0: Failed RT validation. (Verified Mapping = 0) 100: The supplier has a strong indication that this account is invalid. (Verifi…
Account
object
15 properties
Payment
object
A Trustly Payment
34 properties 25 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

paywithmybank-payments-api-openapi.yml Raw ↑

Other APIs PayWithMyBank (Trustly) publishes across the network.

PayWithMyBank (Trustly) accountData API
PayWithMyBank (Trustly) accounts API
PayWithMyBank (Trustly) countries API
PayWithMyBank (Trustly) customers API
PayWithMyBank (Trustly) disputeManagement API
PayWithMyBank (Trustly) identity API
PayWithMyBank (Trustly) networkCheckApi API
PayWithMyBank (Trustly) paymentProviders API
PayWithMyBank (Trustly) transactions API
PayWithMyBank (Trustly) verifyCustomer API
Where this information came from

This is an independent, third-party profile of PayWithMyBank (Trustly) payments API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.