Yapily
United Kingdom / Europe · open banking: list consented accounts; list account transactions.
Match provider records to your invoices, orders and finance workflows without moving funds.
Source actions
2
Destination actions
0
Data types
2
Validation status
Implemented · fixture tested.
Implementation is checked against provider-shaped fixtures for every action, authentication failures, rate limits, pagination and duplicate safety. Provider sandbox and authorised account validation are recorded separately when credential-backed runs are completed.
What you can map
accounts
- List consented accountsSource
Read account type, currency and balance; omit account numbers and account-holder names.
transactions
- List account transactionsSource
Read consented account transactions with offset pagination.
Authentication
Application ID/secret plus authorised consent token
Plans and access
An approved provider account with API access and the required read scopes. Availability depends on the merchant country, product, permissions and provider agreement.
Test environment
Use dedicated provider test credentials where available; credential-backed validation is pending.
Rate limits
Provider/account-specific limits apply. HTTP 429 and Retry-After are handled with bounded retries.
Provider events
Provider events are not ingested by this adapter. Nexra event triggers are not yet available; flows run on demand or on a schedule.
Before you build a flow
- Read-only bank data under an existing account-holder consent; consent acquisition and renewal must happen outside Nexra.
- No payment initiation or fund transfers. Reauthentication may be required by the bank.
- Provider sandbox and authorised-account validation pending.