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) transactions API

The transactions API from PayWithMyBank (Trustly) — 10 operation(s) for transactions.

PayWithMyBank (Trustly) transactions 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 Transaction. The published artifact set on APIs.io includes an OpenAPI specification.

This API exposes 10 operations across 10 paths, and defines 51 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.

10 operations 10 paths 51 schemas 2 GET8 POST

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) transactions API declares 1 security scheme for authenticating requests. It accepts HTTP basic authentication (HTTPBasic).

Paths & Operations 10

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

transactions 10
POST
/transactions/{transactionId}/cancel
Cancel transaction
post-transactions-cancel 2 params body → 200
POST
/transactions/{transactionId}/capture
Capture transaction
post-transactions-transactionId-capture 2 params body → 200
POST
/transactions/{transactionId}/deposit
Deposit transaction
post-transactions-deposit 2 params body → 200
POST
/establish
Establish a new transaction for authorization
post-establish 4 params body → 200
GET
/transactions
Get transactions
list-transactions 45 params → 200
POST
/transactions/{transactionId}/capture/preAuth
Preauthorize transaction
post-transactions-transactionId-capture-preauth 2 params body → 200
POST
/transactions/{transactionId}/reclaim
Reclaim transaction
post-transactions-transactionId-reclaim 2 params body → 200
POST
/transactions/{transactionId}/refresh
Refresh a transaction
post-transactions-refresh 2 params body → 200
POST
/transactions/{transactionId}/refund
Refund transaction
post-transactions-refund 2 params body → 200
GET
/transactions/{transactionId}
Retrieve a transaction
get-transaction 2 params → 200

Schemas 51

The contract defines 51 schemas that model the data the API accepts and returns. The most detailed are Payment (34 properties), Transaction (29 properties), Customer (21 properties), EstablishData (20 properties). Each schema is shown below with its type and property counts.

Verification
object
3 properties
EstablishPostRequestBodyContentApplicationJsonSchemaCurrency
string
3-letter ISO Currency Code.
TransactionsTransactionIdRefreshPostResponsesContentApplicationJsonSchemaRefresh
object
1 property 1 required
CustomerCustomData
object
Object for sending merchant-specific custom data.
PaymentSystem
string
Financial Institution Account Type: -1: None 1: PayWithMyBank 2: TrustlyAB
Transactions_post-transactions-refresh_Response_200
object
1 property 1 required
PaymentMerchant
object
2 properties
TransactionTransactionType
string
Type of transaction record. See [Transaction Types](/integrate/api-fundamentals/status-codes-and-type-definitionstransaction-types)
Address
object
Valid mailing or billing address associated with the customer
6 properties 1 required
EstablishPostRequestBodyContentApplicationJsonSchemaMetadataFinishButtonLabelType
string
Modify the final button label of the Trustly UI. The default label is "Continue", by passing a supported alternative in this property the button label can be c…
DriverLicense
object
2 properties 2 required
PaymentProviderSubType
string
Financial Institution Account Type: 1000: Online Banking 2000: Manual Entry 2001: Manual Entry with Challenge Deposit
EstablishDataCurrency
string
3-letter ISO Currency Code. Currently only USD is supported.
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…
TransactionStatus
string
Status code of the Payment Provider Transaction record. See [Transaction Types](/integrate/api-fundamentals/status-codes-and-type-definitionstransaction-types)
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.
TrustlyABRequest
object
5 properties
Transaction
object
A Trustly transaction object
29 properties 20 required
EstablishPostRequestBodyContentApplicationJsonSchemaMetadataClc
object
Properties relating to Trustly In-Person configuration. Required for Trustly In-Person apps.
4 properties
Attribute
object
2 properties
EstablishPostRequestBodyContentApplicationJsonSchemaBeneficiary
object
The ultimate beneficiary of this payment. Required when using paymentType: Instant for [Money Transfer](/integrate/send-money)
8 properties
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.
TransactionsTransactionIdCapturePreAuthPostRequestBodyContentApplicationXWwwFormUrlencodedSchemaMetadataRemittanceWithdrawalMethod
string
The method by which the recipient will receive the funds.
Transactions_list-transactions_Response_200
object
1 property
EstablishDataKycType
string
Specifies the KYC (Know Your Customer) type as number. The possible value is 1 (OnlineBanking). This field is optional and can only be used by merchants config…
EstablishPostRequestBodyContentApplicationJsonSchemaMetadataIntegrationContext
string
Configuration required for mobile app compatibility with OAuth bank login flows. More details can be found in the [OAuth and Mobile apps guide](doc:oauth-guide…
VerificationMode
string
Verification Mode: 1: VerifiedByMerchant 2: ApprovedByMerchant 3: VerifiedByTrustly 4: AmountAuthorizedByMerchant
PaymentProviderSubtype
string
Payment Provider Subtype: 1000: EasyOnline 2000: MEC 2001: MCD
PaymentProvider
object
Details of the Financial institution
9 properties 1 required
EstablishPostRequestBodyContentApplicationJsonSchemaMetadata
object
Provide additional use case-specific properties in this object.
5 properties
PaymentProviderTransactionPaymentProcessor
object
6 properties
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
EstablishPostRequestBodyContentApplicationJsonSchemaPaymentType
string
Specifies the type of transaction to create. Possible values are Instant, Deferred, Disbursement, Recurring, Verification, and Retrieval. Default is Retrieval.…
PaymentAuth
object
3 properties
Recurrence
object
Recurring payment options
10 properties
TransactionCurrency
string
3-letter ISO Currency Code. Currently only USD is supported.
PaymentProviderTransaction
object
Payment Provider Transaction
9 properties
TransactionsTransactionIdCapturePostRequestBodyContentApplicationXWwwFormUrlencodedSchemaMetadataRemittanceWithdrawalMethod
string
The method by which the recipient will receive the funds.
PaymentPaymentType
string
Financial Institution Account Type: 1: Instant - Instant payment. The debit instruction is automatically initiated with that day's batch after consumer authori…
EstablishPostRequestBodyContentApplicationJsonSchemaBeneficiaryAccount
object
Financial institution account associated with the ultimate beneficiary of a transaction. Required when using paymentType: Instant for [Money Transfer](/integra…
3 properties
EstablishPostRequestBodyContentApplicationJsonSchemaAccount
object
Account information. Required if paymentType is Verification and a transactionId is not included.
3 properties
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
EstablishData
object
establishData is required to establish a new user authorization or to launch the Trustly UI for any other reason
20 properties 1 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

paywithmybank-transactions-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) payments API
PayWithMyBank (Trustly) verifyCustomer API
Where this information came from

This is an independent, third-party profile of PayWithMyBank (Trustly) transactions 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.