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

Lean Technologies Account On File API

The Account On File API from Lean Technologies — 2 operation(s) for account on file.

Lean Technologies Account On File API is one of 67 APIs that Lean Technologies publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

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

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

Requests are made against 2 base URLs: https://sandbox.leantech.me, https://api2.leantech.me.

2 operations 2 paths 43 schemas 2 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.1.0
API Version
v0.2.3
Base URL
https://api2.leantech.me
Authentication
HTTP Bearer
Resource Areas
1

Authentication & Security 1

Lean Technologies Account On File API declares 1 security scheme for authenticating requests. It accepts HTTP bearer tokens (bearerAuth). By default, every request must be authenticated.

Paths & Operations 2

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

Account On File 2
POST
/consents/account-on-file
Create a new non-authorized AoF consent
createAccountOnFileConsent body → 200
POST
/payments/account-on-file
Initiate a AoF payment
1 param body → 200

Schemas 43

The contract defines 43 schemas that model the data the API accepts and returns. The most detailed are DeviceInformation (18 properties), Payments20InitiateAccountOnFilePaymentResponse (13 properties), Address (11 properties), DebtorIndicators (10 properties). Each schema is shown below with its type and property counts.

AppInformation
object
Mobile application specific information.
3 properties
PeriodType
string
Defines the time period used for applying limits on a long‑lived consent. This value determines how consumption limits (e.g., maximum amounts or number of paym…
ScreenInformation
object
2 properties
AccountRiskIndicators
object
Risk indicators related to the account.
5 properties
PossessionFactor
object
The User's possession, that only the User possesses
2 properties
Currency
string
The ISO 3 letter currency code.
GeoLocation
object
GPS to identify and track the whereabouts of the connected electronic device.
2 properties
TransactionHistory
object
2 properties
ChannelType
string
Where the payment has been initiated from
TransactionIndicators
object
7 properties 1 required
DeviceType
string
AccountOnFileControlParameters
object
Defines the control parameters for a Account On File (AoF) consent. These parameters specify the applicable limits for individual payments, cumulative amounts,…
6 properties 1 required
ConnectionType
string
DebtorIndicators
object
Debtor (User) Indicators
10 properties
ReorderItemsIndicator
string
Indicates if the transaction is a reorder
Authentication
object
The authentication method used by the User to access their account
8 properties
Reference
string
A reason or reference in relation to a payment. Maximum 64 chars
DeliveryTimeframe
string
Timeframe for the delivery of purchased items
CurrencyAmount
object
2 properties 2 required
BatteryStatus
object
2 properties
RiskDetails
object
The Risk section is used to specify additional details for risk/fraud scoring regarding Payments
3 properties
Payments20InitiateAccountOnFilePaymentResponse
object
13 properties 10 required
ScrollBehavior
object
3 properties
PreOrderPurchaseIndicator
string
Indicates if this is a pre-ordered item
BrowserInformation
object
Browser-specific information
5 properties
InherenceType
string
DestinationDeliveryAddress
object
3 properties
DeviceManufacturer
object
2 properties
PaymentPurposeCode
string
A category code that relates to the type of services or goods that corresponds to the underlying purpose of the payment. The code must conform to the payment p…
DeviceEnvironmentContext
string
TouchSupport
object
2 properties
BiometricType
string
Name
object
2 properties
MotionSensors
object
3 properties
BiometricCapabilities
object
2 properties
AddressMatchLevel
string
Level of match between delivery and billing addresses
UserBehavior
object
1 property
MerchantRisk
object
6 properties 6 required
KnowledgeFactor
object
The User's knowledge, that only the User knows
2 properties
DeviceInformation
object
Detailed device information
18 properties
Address
object
11 properties 2 required
GovernmentIdentifierRequest
object
2 properties 2 required
InherenceFactor
object
The User's inherence, that is unique to the User's physical characteristics
2 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

lean-technologies-account-on-file-api-openapi.yml Raw ↑

Other APIs Lean Technologies publishes across the network.

Lean Technologies Account Controls (New) API
Lean Technologies Accounts Raw Data API
Lean Technologies Assets API
Lean Technologies Balance Raw Data API
Lean Technologies Balances API
Lean Technologies Bank API
Lean Technologies Bank Statements Report API
Lean Technologies Banks API
Lean Technologies Behavioral Insights (New) API
Lean Technologies Beneficiaries Raw Data API
Lean Technologies Beneficiary Name Verification API
Lean Technologies Cashflow Patterns (New) API
Where this information came from

This is an independent, third-party profile of Lean Technologies Account On File 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.