Finqware

Introduction

### Overview

FinqLink is a set of APIs for account-to-account payments/transfers ([FinqLink Pay](https://developers.finqware.com/api-reference/pay-apis)) and account information services ([FinqLink Data](https://developers.finqware.com/api-reference/data-apis)) through open-banking and other local/custom integrations.

### How to test

1. Get a set of API test credentials (contact Finqware)
2. Use the /test/providers/list endpoint to query for the available/supported providers.
  - to visualize the providers list (and more) check our public [dashboard](https://pay.finqware.com/web/v2/providers).
3. Create finq-links using the `/test` path:
  - payment links using the `/test/links/create` endpoint
  - consent links for account data using the `/test/consents/create` endpoint.
4. Send the link to someone in order to authorize the payment or to authorize access to account data.

### Sandbox testing

- `rzb_ro` - debtor IBAN: `RO03RZBR0000069999999999`, creditor IBAN: `RO10RZBR0000069999999970`, PSU ID: `9999999998`
- `bt_ro` - username: `testbt`, password: `testbt`, pin: `1234567`
- `cec_ro` - username: `testcecapi`, password: `testcecapi`, IBAN: `RO42CECEAG0202RON0007466`
- `granit_hu` - username: `testuser`, password: `testuser`, SMS code: `SMS`
- `mbh_hu` - username: `testuser`, password: `testuser`, SMS code: `SMS`


🚀 Quick Start

### Version 2.0 Changelog

This document outlines all changes between FinqLink API v1 and v2, including new features, enhancements, and breaking changes.

---

#### Overview

FinqLink v2 is a major release that introduces:

- **FinqLink Data (Beta)** - Account Information Services (AIS) for accessing bank account data
- **Enhanced Pay APIs** - Pagination, filtering, and new link statuses
- **Custom WebUI Templates** - 7 customizable UI themes for payment and consent flows
- **Providers API Enhancements** - AIS methods support and improved response formats

---

#### New: Account Information Services (AIS) - FinqLink Data

The most significant addition in v2 is the complete **Account Information Services (AIS)** functionality, branded as **FinqLink Data**. This enables bank account data access alongside existing payment initiation capabilities.

> **Note:** FinqLink Data is currently in **Beta**. Contact Finqware to enable AIS access for your API client.

##### New API Endpoints

All AIS endpoints are available on `/v2` API paths only (not available in v1):

<Table style="width:100%;min-width:100%" colSizes='["initial", "initial"]' isHeaderAdded='true' tableHeader='[{"id": "5c7ce57a-9a66-465e-a960-03789fd59e2b", "title": "Endpoint"}, {"id": "686b5b9c-6317-44ab-8168-656e59e2f000", "title": "Description"}]'>
  <table-row>
    <table-cell>POST /ais/consents/create</table-cell>
    <table-cell>Create a new AIS consent for data access</table-cell>
  </table-row>
  <table-row>
    <table-cell>POST /ais/consents/get</table-cell>
    <table-cell>Retrieve consent details and current status</table-cell>
  </table-row>
  <table-row>
    <table-cell>POST /ais/consents/revoke</table-cell>
    <table-cell>Revoke an active consent</table-cell>
  </table-row>
  <table-row>
    <table-cell>POST /ais/consents/redirect</table-cell>
    <table-cell>Handle SCA callback redirect (direct_sca flow)</table-cell>
  </table-row>
  <table-row>
    <table-cell>POST /ais/transactions/list</table-cell>
    <table-cell>List transactions with filtering and keyset pagination</table-cell>
  </table-row>
  <table-row>
    <table-cell>POST /ais/accounts/list</table-cell>
    <table-cell>List accounts with balance information</table-cell>
  </table-row>
  <table-row>
    <table-cell>POST /ais/balances/list</table-cell>
    <table-cell>List balance history with pagination</table-cell>
  </table-row>
  <table-row>
    <table-cell>POST /ais/jobs/create</table-cell>
    <table-cell>Trigger an on-demand data refresh job</table-cell>
  </table-row>
  <table-row>
    <table-cell>POST /ais/jobs/get</table-cell>
    <table-cell>Get data refresh job status</table-cell>
  </table-row>
</Table>

##### Consent Lifecycle

AIS consents follow this lifecycle:

```
created → started → requested → sca_url_retrieved → awaiting_authz → authorized → active
```

**Terminal states:** `expired`, `revoked`, `deactivated`, `failed`, `suspended`

##### Scope Configuration

Control what data is accessible through consent scope:

- **Full scope:** `["accounts", "balances", "transactions"]` - Access to all account data
- **Limited scope:** `["accounts", "balances"]` - Faster job completion, no transaction history

##### AIS Webhooks

Configure webhooks in consent creation to receive real-time updates:

- **`consent_status_update`** - Triggered when consent status changes (e.g., `awaiting_authz` → `active`)
- **`job_status_update`** - Triggered when data refresh job completes or fails

---

#### Enhanced: Links API

##### Pagination for `/links/list`

The `/links/list` endpoint now supports **keyset-based pagination** for efficient traversal of large result sets.

**Request parameters:**

```json
{
  "pagination": {
    "limit": 50,
    "after": "eyJpbnNlcnRlZF9hdCI6..."
  }
}
```

<Table style="width:100%;min-width:100%" colSizes='["initial", "initial", "initial"]' isHeaderAdded='true' tableHeader='[{"id": "66cfaa92-25a7-4d71-9aae-6f07f4421d59", "title": "Parameter"}, {"id": "def6ff38-7d19-4732-ae74-f46a4298fbac", "title": "Type"}, {"id": "b6177084-88b6-4fcb-b468-1d60f8969af1", "title": "Description"}]'>
  <table-row>
    <table-cell>pagination.limit</table-cell>
    <table-cell>integer</table-cell>
    <table-cell>Maximum records per page (1-250, default: 50)</table-cell>
  </table-row>
  <table-row>
    <table-cell>pagination.after</table-cell>
    <table-cell>string</table-cell>
    <table-cell>Keyset cursor from previous response for next page</table-cell>
  </table-row>
</Table>

**Response includes:**

```json
{
  "pagination": {
    "count": 50,
    "more?": true,
    "after": "eyJpbnNlcnRlZF9hdCI6Li4u"
  },
  "links": [...]
}
```

##### New Filter Options

Filter payment links by multiple criteria:

<Table style="width:100%;min-width:100%" colSizes='["initial", "initial", "initial"]' isHeaderAdded='true' tableHeader='[{"id": "ab1dbd40-c4fc-4732-8f0f-016c8c92182c", "title": "Filter"}, {"id": "0a9dc2e5-ee0b-4466-905b-f5bacdf02f2e", "title": "Type"}, {"id": "5562f6c8-c754-4d70-b7f4-4f797d1704f9", "title": "Description"}]'>
  <table-row>
    <table-cell>filter.status</table-cell>
    <table-cell>string</table-cell>
    <table-cell>Filter by payment status (created, completed, failed, etc.)</table-cell>
  </table-row>
  <table-row>
    <table-cell>filter.inserted_at_from</table-cell>
    <table-cell>datetime</table-cell>
    <table-cell>Links created after this timestamp</table-cell>
  </table-row>
  <table-row>
    <table-cell>filter.inserted_at_to</table-cell>
    <table-cell>datetime</table-cell>
    <table-cell>Links created before this timestamp</table-cell>
  </table-row>
</Table>

**Example:**

```json
{
  "filter": {
    "status": "completed",
    "inserted_at_from": "2024-01-01T00:00:00Z"
  },
  "pagination": {
    "limit": 100
  }
}
```

##### New Payment Link Statuses

Additional statuses for enhanced payment tracking (available for libra_ro, work-in-progress for other providers):

<Table style="width:100%;min-width:100%" colSizes='["initial", "initial"]' isHeaderAdded='true' tableHeader='[{"id": "a5030bbc-a9e2-4a32-9ede-06a382a8d46a", "title": "Status"}, {"id": "79c546f6-7e6e-4cfe-bc3c-11ff1c57735b", "title": "Description"}]'>
  <table-row>
    <table-cell>funds_received</table-cell>
    <table-cell>Funds confirmed received by creditor bank (via webhook)</table-cell>
  </table-row>
  <table-row>
    <table-cell>funds_rejected</table-cell>
    <table-cell>Funds rejected by creditor bank (via webhook)</table-cell>
  </table-row>
</Table>

---

#### Enhanced: Providers API

##### AIS Methods Support

The `/providers/list` and `/providers/get` endpoints now support AIS method discovery:

**New options:**

<Table style="width:100%;min-width:100%" colSizes='["initial", "initial", "initial"]' isHeaderAdded='true' tableHeader='[{"id": "9823cd86-260c-4dea-abfd-3244127d9d8c", "title": "Option"}, {"id": "dc5031b0-e5dd-4954-9095-b50d9b042094", "title": "Type"}, {"id": "99ff1fda-8a1e-4492-837d-4889a6478a0a", "title": "Description"}]'>
  <table-row>
    <table-cell>options.show_ais_methods</table-cell>
    <table-cell>boolean</table-cell>
    <table-cell>Include AIS method details in response</table-cell>
  </table-row>
  <table-row>
    <table-cell>options.ais_methods_filter.account_owner_type</table-cell>
    <table-cell>array</table-cell>
    <table-cell>Filter by account owner type (retail, corporate)</table-cell>
  </table-row>
  <table-row>
    <table-cell>options.ais_methods_filter.interface_type</table-cell>
    <table-cell>string</table-cell>
    <table-cell>Filter by interface type</table-cell>
  </table-row>
  <table-row>
    <table-cell>options.ais_methods_filter.interface_env</table-cell>
    <table-cell>string</table-cell>
    <table-cell>Filter by environment (sandbox, stage, prod)</table-cell>
  </table-row>
</Table>

**Example:**

```json
{
  "options": {
    "show_ais_methods": true,
    "ais_methods_filter": {
      "account_owner_type": ["retail"],
      "interface_env": "prod"
    }
  }
}
```

##### Response Format Change: `remitter_type`

The `remitter_type` field format has changed between v1 and v2:

<Table style="width:100%;min-width:100%" colSizes='["initial", "initial", "initial"]' isHeaderAdded='true' tableHeader='[{"id": "6b667f89-56bf-442f-87da-fb99e619b58d", "title": "Version"}, {"id": "6ac04005-bec5-4101-b7e7-3e7793a62c7d", "title": "Format"}, {"id": "f4eaccae-6048-4499-be7b-5830ee3a9dc9", "title": "Example"}]'>
  <table-row>
    <table-cell>v1</table-cell>
    <table-cell>String</table-cell>
    <table-cell>"retail" or "corporate"</table-cell>
  </table-row>
  <table-row>
    <table-cell>v2</table-cell>
    <table-cell>Array</table-cell>
    <table-cell>["retail"], ["corporate"], or ["retail", "corporate"]</table-cell>
  </table-row>
</Table>

This change enables payment methods to support multiple remitter types simultaneously.

---

#### New: WebUI Custom Templates

Customize the payment and consent authorization UI with pre-built templates.

##### Available Templates

<Table style="width:100%;min-width:100%" colSizes='["initial", "initial"]' isHeaderAdded='true' tableHeader='[{"id": "c02228da-0e2c-4fe1-94f3-a2dda9ccc73f", "title": "Template"}, {"id": "0c5b6fba-278a-4c18-9be6-4d8f2d0d9f55", "title": "Description"}]'>
  <table-row>
    <table-cell>default</table-cell>
    <table-cell>Standard/legacy FinqLink layout</table-cell>
  </table-row>
  <table-row>
    <table-cell>classic</table-cell>
    <table-cell>Traditional banking interface</table-cell>
  </table-row>
  <table-row>
    <table-cell>compact</table-cell>
    <table-cell>Minimal, space-efficient layout</table-cell>
  </table-row>
  <table-row>
    <table-cell>cards</table-cell>
    <table-cell>Card-based provider selection</table-cell>
  </table-row>
  <table-row>
    <table-cell>glass</table-cell>
    <table-cell>Glassmorphism design with blur effects</table-cell>
  </table-row>
  <table-row>
    <table-cell>sheet</table-cell>
    <table-cell>Bottom sheet mobile-first design</table-cell>
  </table-row>
</Table>

##### Usage

Specify the template in `/links/create` or `/ais/consents/create`:

```json
{
  "options": {
    "ux_template": "glass"
  }
}
```

> **Note:** The `ux_template` option overrides the default template configured for your API client.

---

#### Breaking Changes

##### 1. `remitter_type` Response Format

**Affected endpoints:** `/providers/list`, `/providers/get`

The `remitter_type` field in payment method responses has changed from a string to an array:

**v1 Response:**
```json
{
  "payment_methods": [{
    "remitter_type": "retail"
  }]
}
```

**v2 Response:**
```json
{
  "payment_methods": [{
    "remitter_type": ["retail"]
  }]
}
```

**Migration:** Update your code to handle `remitter_type` as an array.

##### 2. AIS Endpoints Availability

AIS endpoints (`/ais/*`) are **only available on /v2 paths**. Requests to `/v1/ais/*` will return a 404 error.

##### 3. Pagination Response Structure

The `/links/list` endpoint now returns pagination metadata in a structured format:

**v1 Response:**
```json
{
  "links": [...]
}
```

**v2 Response:**
```json
{
  "pagination": {
    "count": 50,
    "more?": true,
    "after": "cursor_token"
  },
  "links": [...]
}
```

**Migration:** Update your code to extract links from the `links` array and handle pagination metadata.

---

#### Migration Guide

##### Upgrading from v1 to v2

1. **Update API path:** Change from `/v1/` to `/v2/`
2. **Handle array `remitter_type`:** Update providers response parsing to treat `remitter_type` as an array
3. **Optional**: If using `/links/list`, handle the new pagination response structure
4. **Optional - Enable AIS:** Contact Finqware to enable FinqLink Data access for your API client
5. **Optional - Customize UI:** Explore the new `ux_template` options for branded payment experiences

##### API Version Support

<Table style="width:100%;min-width:100%" colSizes='["initial", "initial", "initial"]' isHeaderAdded='true' tableHeader='[{"id": "bbbacb07-d4e4-449f-b8a1-b7f6ce1480d4", "title": "Version"}, {"id": "3ebb2654-3a35-42f7-9c68-9be52259f218", "title": "Status"}, {"id": "67126568-22e2-486d-9c85-1c8e7f03aafe", "title": "End of Life"}]'>
  <table-row>
    <table-cell>v1</table-cell>
    <table-cell>Supported</table-cell>
    <table-cell>TBD</table-cell>
  </table-row>
  <table-row>
    <table-cell>v2</table-cell>
    <table-cell>Current</table-cell>
    <table-cell>-</table-cell>
  </table-row>
</Table>


📋 Changelog

API Reference

The Link API is secured by OAuth2 (mandatory for production access) and mTLS (optional).

Mutual TLS (mTLS) and OAuth2 Client Credentials are two distinct security mechanisms that can complement each other to provide robust authentication and secure communication in API integrations.

> **Note:** For testing purposes we also support an internal authentication method that requires `client_id`/`client_secret` with each API call. The code examples in this document use this particular method.

### How mTLS and OAuth2 Client Credentials Complement Each Other

When used together, mTLS and OAuth2 Client Credentials Grant provide a powerful combination of strong client authentication and fine-grained authorization. Here's how they complement each other:

### Dual Authentication and Authorization

- mTLS provides a strong, cryptographic client authentication mechanism, ensuring that only authorized clients (those with valid client certificates) can establish a connection.
- OAuth2 Client Credentials provides a token-based mechanism for authorizing the client's access to specific APIs or resources. The access token contains information about the client's permissions and access scope.

### Layered Security

By using both mTLS and OAuth2, you establish multiple layers of security. Even if an access token is somehow obtained by an attacker, mTLS ensures that only clients with a valid certificate can connect. Conversely, even if a client possesses a valid certificate, it still needs a valid access token to access protected resources.

### Preventing Token Theft and Replay Attacks

With mTLS, the secure communication channel prevents token theft during transmission. Even if a token were somehow intercepted, it would be useless without the client's certificate to establish the connection.

### Enhanced Security for Sensitive Applications

For highly sensitive applications, combining mTLS with OAuth2 Client Credentials ensures that only authenticated clients (validated by their certificates) and authorized clients (validated by their tokens) can access resources. This is particularly important in zero-trust environments or for internal microservices communication.

### Compliance and Regulatory Requirements

Some industries require strong client authentication and end-to-end encryption. Combining mTLS with OAuth2 can help meet these regulatory requirements by ensuring secure communication and controlled access.

### Summary

By combining mTLS with OAuth2 Client Credentials Grant, you gain the benefits of both strong client authentication and fine-grained access control, enhancing the overall security posture of your application.


Security

Payment initiation and provider discovery endpoints.

### Overview

FinqLink Pay is a set of APIs for account-to-account payments/transfers through open-banking and other local/custom integrations (eg: RoPay in Romania).

The platform enables API clients to create payment links that allow end-users to complete payments through
their banking providers using Strong Customer Authentication (SCA).

Pay-by-link is a method that breaks the payment process in two distinct phases:

- the creation of a payment request, operated by the creditor (receiver of funds)
- the acceptance & authorization of the payment, operated by the debtor (the source of funds)

The payment request encapsulates metadata such as: amount, currency, the list of goods to be acquired etc. Once its created, the payment request is wrapped into a transportable object - aka the link- such as a URL or a QR code. The link is sent to a debtor who will only check/approve & authorize the payment.

### Payment providers

A payment-provider is a partner institution that operates payment services. FinqLink integrates with these providers over APIs such as open-banking payment initiation APIs.
Each provider has a unique code. Eg: `rzb_ro`, `cec_ro` etc.
A provider may have one or multiple payment-methods offering different capabilities (domestic-only transfers, corporate-only transfers etc)
we provide an API and a [dashboard](https://pay.finqware.com/web/v2/providers) for quering and visualising all the details regarding providers & methods.

### Payment Flow Types
The API supports multiple payment flow types:
- **link**: Default web-based payment experience via FinqLink WebUI
- **wrapped_sca**: SCA URLs wrapped in a transportable link operated via FinqLink WebUI
- **direct_sca**: Mobile app-to-app experience with direct bank redirect (requires a custom eIDAS certificates setup)
- **redirect_sca**: Mobile app-to-app experience with redirect via FinqLink WebUI

### The FinqLink Pay WebUI

The WebUI is a web application that facilitates the payment process by providing a user interface for the end-user to complete the payment.
It comes with a payment-method selection component, payment details and real-time status updates.

![FinqLink Pay WebUI](https://d24lr4zqs1tgqh.cloudfront.net/b0c679fe-4d42-41a1-8f3f-59bf8af00056-693c10b7ef5867a056b9d195.png)

### Webhooks
The API supports webhook notifications for payment status updates.
Configure webhook URLs when creating payment links. Webhook payloads include:
- `type`: Event type (e.g., "link_status_update")
- `link_id`: The payment link UUID
- `web_id`: The public web identifier
- `status`: New payment status

### Decimal Values
Monetary amounts are represented as strings to maintain precision (e.g., "100.50").
- No leading zeros allowed (except for values less than 1, e.g., "0.50")
- No comma separators allowed
- Decimal point is optional for whole amounts


Pay APIs

Account Information Services (AIS) endpoints for accessing banking data.

Note: This API is in public beta and may be slightly changed based on your feedback.

Webhooks are supported for:
- **Consent status updates**: Notified when consent status changes (e.g., `started` → `active`)
- **Job status updates**: Notified when data refresh jobs complete or change status

Banking data retrieval endpoints for accounts, balances, and transactions.

### Pagination
The transactions and balances list endpoints use keyset-based pagination.
Use the `keyset` value from the last record as the `after` parameter
in your next request to fetch the next page.

### Filtering
All data endpoints support filtering by various criteria:
- Accounts: currency, account type
- Balances: currency, type, account ID
- Transactions: amount range, date range, credit/debit indicator, status

### Balance Types
Check the [balance types](data-apis/data/list-balances) documentation for more details.


Data APIs

FinqLink APIs

Finqware Link API

Testing server (client_id/client_secret)

Testing server (OAuth2)

Production server (OAuth2)

Consents

Create Consent

Get Consent

Handle Redirect

Revoke Consent

Data

List Accounts

List Balances

List Transactions

Jobs

Create Data Refresh Job

Get Data Refresh Job

Links

Create Link

Get Link

List Links

Providers

Get Provider

List Providers

mTLS

OAuth2

Webhook signing and callbacks

Create, retrieve, and manage payment links for open-banking transactions

Creates a new payment link for initiating a bank transfer through open-banking.
Returns a web URL where the end-user can complete the payment through their bank's
Strong Customer Authentication (SCA) flow.

### Payment Flow Types
The `type` option determines how the payment link is created and the user experience:

<Table style="width:100%;min-width:100%" colSizes='["initial", "initial", "initial"]' isHeaderAdded='true' tableHeader='[{"id": "ded7f171-463e-44d3-b831-a5339f7a9ce7", "title": "Type"}, {"id": "3515c3b3-200c-418c-8e75-c511790d130d", "title": "Behavior"}, {"id": "1b14767f-5b18-421f-a089-3adc03e10813", "title": "Use Case"}]'>
  <table-row>
    <table-cell>link</table-cell>
    <table-cell>Returns a transportable payment link, end-user opens it in [FinqLink WebUI](api-reference/pay-apis#The-FinqLink-Pay-WebUI) to complete the payment. Offers maximum flexibility in terms of expiration and user optionality. Use this flow when generating payment links expected to be operated after a longer time. Example: an invoice sent over email which you don't expect an immediate action for.</table-cell>
    <table-cell>Invoicing, QR codes</table-cell>
  </table-row>
  <table-row>
    <table-cell>direct_sca</table-cell>
    <table-cell>A non-transportable payment link. The API returns a native authorisation URL received from the payment provider and your application will process the redirect call from the payment provider. Available under certain custom requirements (discuss with a Finqware representative).</table-cell>
    <table-cell>Mobile app-to-app experience</table-cell>
  </table-row>
  <table-row>
    <table-cell>wrapped_sca</table-cell>
    <table-cell>A transportable payment link for immediate usage. The authorisation URL is requested at link creation, hence there is no optionality anymore for the user to choose a different payment provider. Use this flow when (1) you know upfront all the payment details and (2) you expect immediate action from your user, as the authorisation URL may expire in minutes.</table-cell>
    <table-cell>E-commerce, invoicing</table-cell>
  </table-row>
  <table-row>
    <table-cell>redirect_sca</table-cell>
    <table-cell>Similar to direct_sca, but handles redirects through WebUI</table-cell>
    <table-cell>App-to-app UX</table-cell>
  </table-row>
</Table>

### Payment Method Selection
Use the `payment_method` object as a filter to restrict the available payment methods:
- Filter by specific banks (`provider_id`)
- Filter by account type (`remitter_type`: retail and/or corporate)
- Filter by payment rails (`payment_scheme`: instant, domestic, SEPA)
- Filter by environment (`env`: sandbox, stage, prod)

The WebUI selector component will only show the payment methods that match the filter.

Example if you want to restrict your user to pay from their personal account from a list of specific banks:
```json
{
  "payment_method": {
    "provider_id": ["bt_ro", "ing_ro", "bcr_ro"],
    "remitter_type": ["retail"],
    "env": "prod"
  }
}
```


Retrieves detailed information about a specific payment link.
Returns the current status, expiration, selected payment method, and service provider details.

### Response Fields
- `status`: Current payment status (see LinkStatus enum for possible values)
- `is_expired`: Whether the link has expired
- `payment_method`: Details of the selected payment method (if user has selected one)
- `service_provider`: Details of the selected bank (if user has selected one)


Retrieves payment links owned by the authenticated API client with optional filtering and pagination.
Returns a summary of each link including status, expiration, and web URL.

**Note**: Only returns links created by the authenticated API client.

### Filtering
Use the `filter` object to narrow down links by:
- `status`: Filter by payment status (created, completed, failed, etc.)
- `inserted_at_from` / `inserted_at_to`: Filter by creation date range

### Pagination
Uses keyset-based pagination for efficient traversal of large result sets.
Use the `keyset` value from the last link in the current page as the `after`
parameter in your next request to fetch the next page.


Handles the callback redirect from the bank's SCA authentication flow.
Used only for `direct_sca` payment flows where the bank redirects back
to your provided endpoint (custom setup with each bank required).

### Execution Modes
- **Async (default)**: Returns immediately with status `redirect_in_progress`
- **Sync**: Waits for final payment status (completed, failed, or submitted)

### Response Status Codes
- `200`: Redirect processed successfully
- `201`: Redirect already processed (idempotent retry)
- `202`: Redirect in progress (async mode or concurrent request)

**Note**: This endpoint is available for selected customers only (licensed entities).


Discover available banks and payment methods for payment initiation.

Payment provider discovery endpoints for querying available banks and payment methods.

Use these endpoints to discover which banks are available for payment initiation,
their capabilities, and validation schemas for payment intents.

## Filtering
- Filter providers by country code (e.g., "ro" for Romania)
- Filter by specific provider identifiers

## Payment Methods
Each provider may have multiple payment methods with different:
- Account types (retail/corporate)
- Payment schemes (instant, domestic, SEPA)
- Environment availability (sandbox, stage, prod)

## Validation Schemas
Request validation schemas to ensure payment intents meet each bank's requirements.


Sections

Links

What made this section helpful for you?

What made this section unhelpful for you?

Endpoints

What made this section helpful for you?

What made this section unhelpful for you?

Sections

Links

What made this section helpful for you?

What made this section unhelpful for you?

Endpoints

What made this section helpful for you?

What made this section unhelpful for you?

Ask an AI

Code with AI