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

Yodlee Payment Processor API

Yodlee's payment processor partners can use the Payment Processor endpoints to access verified account details using the processorToken created and shared by mutual customers. These APIs are only for payment processor partners and not for developers using the Yodlee services to integrate with payment partners. Refer here for a guide on working with payment processor partners.As a processor payment partner, you can retrieve the following account information using the processorToken:Account details include account status, account name, full account number, bank transfer code, balance, etc.Account holder details include name, email, phone number, address, etc.Account balance details.You will have to set the header before making the API call. The following headers apply to all the APIs:Authorization: This header holds the access token Note: If there are any API-specific headers, they are mentioned explicitly in the respective API's description.

Yodlee Payment Processor API is one of 23 APIs that Yodlee publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Payment Processor. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, and a getting-started guide.

This API exposes 3 operations across 3 paths, and defines 17 schemas. It is described by OpenAPI 3.2.0, at version 1.1.0.

Requests are made against a single base URL, /.

3 operations 3 paths 17 schemas 3 GET

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
1.1.0
Base URL
https://production.api.yodlee.com/ysl
Terms of Service
Resource Areas
1

Paths & Operations 3

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

Payment Processor 3

Yodlee's payment processor partners can use the Payment Processor endpoints to access verified account details using the processorToken created and shared by mutual customers.

GET
/partner/paymentProcessor/account/holder
Get Account Holder Details
getVerifiedAccountHolder 1 param → 200400401404
GET
/partner/paymentProcessor/account/balance
Get Account Balance
getVerifiedAccountBalance 1 param → 200400401404
GET
/partner/paymentProcessor/account
Get Account Details
getVerifiedAccount 1 param → 200400401404

Schemas 17

The contract defines 17 schemas that model the data the API accepts and returns. The most detailed are AccountAddress (10 properties), PaymentAccount (9 properties), PaymentAccountBalance (7 properties), PaymentAccountHolder (7 properties). Each schema is shown below with its type and property counts.

Identifier
object
2 properties
PaymentAccount
object
9 properties
Name
object
4 properties
PaymentAccountHolderResponse
object
1 property
Email
object
2 properties
PaymentAccountBalanceResponse
object
1 property
PaymentAccountBalance
object
7 properties
Money
object
4 properties
PhoneNumber
object
2 properties
AccountProfileDetail
object
4 properties
AccountAddress
object
10 properties
PaymentBankTransferCodeData
object
2 properties
AccountHolderData
object
4 properties
FullAccountNumbers
object
2 properties
YodleeError
object
3 properties
PaymentAccountHolder
object
7 properties
PaymentAccountResponse
object
1 property

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

yodlee-payment-processor-api-openapi.yml Raw ↑

Other APIs Yodlee publishes across the network.

Yodlee Account Verification API
Yodlee FastLink
Yodlee Account Token API
Yodlee Accounts API
Yodlee Auth API
Yodlee Cobrand API
Yodlee Configs API
Yodlee Consents API
Yodlee DataExtracts API
Yodlee Derived API
Yodlee Documents API
Yodlee Holdings API
Where this information came from

This is an independent, third-party profile of Yodlee Payment Processor 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.