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

The identity API from PayWithMyBank (Trustly) — 3 operation(s) for identity.

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

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

3 operations 3 paths 65 schemas 2 GET1 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) identity API declares 1 security scheme for authenticating requests. It accepts HTTP basic authentication (HTTPBasic).

Paths & Operations 3

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

identity 3
GET
/transactions/{transactionId}/user
Get user
get-trustly-id-user-data 3 params → 200400
GET
/transactions/{transactionId}/user/detail
Get user verification details
get-trustly-id-user-details 3 params → 200400
POST
/transactions/{transactionId}/feedback
Update user status
post-transaction-feedback 2 params body → 200401

Schemas 65

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

Verification
object
3 properties
ScreeningResult
array
CustomerCustomData
object
Object for sending merchant-specific custom data.
PaymentSystem
string
Financial Institution Account Type: -1: None 1: PayWithMyBank 2: TrustlyAB
TransactionsTransactionIdUserDetailGetParametersExpandSchemaItems
string
AdversityMediaScreeningResult
object
Screening information for Adversity Media Screening.
8 properties
AttributeVerificationDetailName
string
Which attribute does this entry refer to.
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
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…
TransactionsTransactionIdUserGetParametersExpandSchemaItems
string
Get-trustly-id-user-detailsRequestBadRequestError
object
1 property 1 required
TransactionStatus
string
Status code of the Payment Provider Transaction record. See [Transaction Types](/integrate/api-fundamentals/status-codes-and-type-definitionstransaction-types)
AttributeVerificationMethod
integer
Indicates which type of verification was performed. It can be: 1 means electronic identity verification. 2 meaning it is manual document verification. 3 meanin…
TransactionsTransactionIdUserDetailGetResponsesContentApplicationJsonSchemaErrorsItems
object
5 properties 5 required
schemas-Address
object
6 properties 1 required
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…
UserVerificationDetailDetail
object
2 properties
WatchlistScreeningResult
object
Screening information for Watchlist Screening.
15 properties
PaymentCurrency
string
3-letter ISO Currency Code. Currently only USD is supported.
ScreeningResultItems
ScreeningResultScreeningType
string
Type of screening being performed. May be: 1: Watchlist Screening. 2: Adverse Media Screening. 3: PEP Screening.
schemas-DriverLicense
object
A driver's license.
2 properties
SchemasAddressCountry
string
2 character ISO Country code. Currently only the US is supported.
Transaction
object
A Trustly transaction object
29 properties 20 required
UserVerificationResult
object
Details on the user verification.
3 properties
PEPScreeningResult
object
Screening information for PEP Screening.
7 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.
AttributeVerification
object
5 properties
AttributeVerificationDetail
object
Attribute details as part of a Trustly ID user verification details
5 properties
UserVerificationErrorCode
string
An error code indicating why the user verification has failed. May be: -1: no error. the verification was successful. 1: there was an internal, unspecified err…
PaymentProviderSubtype
string
Payment Provider Subtype: 1000: EasyOnline 2000: MEC 2001: MCD
VerificationMode
string
Verification Mode: 1: VerifiedByMerchant 2: ApprovedByMerchant 3: VerifiedByTrustly 4: AmountAuthorizedByMerchant
PaymentProvider
object
Details of the Financial institution
9 properties 1 required
SegmentedName
object
The segmented version of a given name.
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.
Post-transaction-feedbackRequestUnauthorizedError
object
1 property 1 required
FinancialInstitutionAccountVerification
object
8 properties 4 required
PaymentProviderCountry
string
2-letter ISO country code of the financial institution
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
TransactionsTransactionIdUserGetResponsesContentApplicationJsonSchemaErrorsItems
object
5 properties 5 required
UserVerificationReason
object
An object describing why an user verification has succeeded or failed.
2 properties
StateCode
string
2 character ISO State code.
PaymentAuth
object
3 properties
User
object
Trustly User
12 properties
UserVerificationDetail
object
1 property
Recurrence
object
Recurring payment options
10 properties
Get-trustly-id-user-dataRequestBadRequestError
object
1 property 1 required
TransactionCurrency
string
3-letter ISO Currency Code. Currently only USD is supported.
WatchlistScreeningResultGender
string
Gender of the user.
AttributeVerificationResult
integer
Indicates the result of the individual attribute verification. It can be: 1 meaning the attribute did not match the expected value. 2 meaning the result was in…
UserVerificationResultCode
string
A code indicating the final outcome of the verification. May be: 1: the verification was rejected. 2: the verification was inconclusive. 3: the verification wa…
PaymentProviderTransaction
object
Payment Provider Transaction
9 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…
BaseException
object
5 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…
AttributeVerificationDetailSource
object
2 properties
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-identity-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) networkCheckApi API
PayWithMyBank (Trustly) paymentProviders API
PayWithMyBank (Trustly) payments API
PayWithMyBank (Trustly) transactions API
PayWithMyBank (Trustly) verifyCustomer API
Where this information came from

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