What is an open banking API?

An open banking API is a standardized interface that allows licensed third-party providers (TPPs) to access bank account information and initiate payments on behalf of customers, with their explicit consent. Banks expose these APIs under regulations such as PSD2 in Europe, the UK Open Banking Standard, or market-driven standards like FDX in the US. Open banking APIs typically support two main service types: Account Information Services (AIS), which read balances and transactions, and Payment Initiation Services (PIS), which initiate bank-to-bank payments. Access is secured via OAuth 2.0 or similar authorization flows, so the customer authorizes the TPP without sharing online banking credentials. The Open Banking Tracker maps 50,000+ banks and their API coverage, plus API aggregators that offer a single integration to many banks. For a full overview, see our Open Banking API guide and API aggregators directory.

An AISP (Account Information Service Provider) is a regulated entity that is licensed to access customers’ bank account data—such as balances and transactions—via open banking APIs, with the customer’s consent. AISPs do not hold or move money; they read data to power account aggregation, credit scoring, budgeting apps, and income verification. In the EU and UK, AISPs operate under PSD2 and the UK Open Banking Standard and must be authorized or registered with the national competent authority (e.g. FCA in the UK). Banks are required to allow licensed AISPs to access accounts through dedicated APIs when the customer has given consent. Many API aggregators (e.g. TrueLayer, Tink, Plaid, Yapily) act as intermediaries between AISPs and banks, offering a single integration to hundreds of banks. The Open Banking Tracker lists AISPs and aggregators by country and capability.

A PISP (Payment Initiation Service Provider) is a regulated entity that can initiate payments from a customer’s bank account to a merchant or another account via open banking APIs, with the customer’s consent. Unlike card payments, the money moves directly between bank accounts (e.g. SEPA, Faster Payments, or ACH). PISPs are licensed under PSD2 in the EU and under the UK Open Banking Standard. They do not handle the funds; they instruct the bank to debit the payer’s account and credit the beneficiary. This supports use cases such as instant checkout, bill pay, and account-to-account transfers with lower fees than cards. Many open banking API aggregators offer both AIS and PIS (payment initiation) so that a single integration can read accounts and initiate payments. The Open Banking Tracker directory lists aggregators by AIS/PIS support and country coverage.

What is account information services (AIS)?

Account Information Services (AIS) are services that allow licensed providers to access a customer’s bank account data—such as balances and transaction history—via open banking APIs, with the customer’s explicit consent. The provider is called an AISP (Account Information Service Provider). AIS does not move money; it only reads data. Typical use cases include account aggregation (showing multiple accounts in one app), income and affordability checks for lending, budgeting and categorization, and business accounting integrations. Under PSD2 and the UK Open Banking Standard, banks must offer dedicated APIs for licensed AISPs. API aggregators often provide AIS (and sometimes PIS) through one integration, so developers can connect to many banks without building to each bank separately. The Open Banking Tracker lists aggregators and their AIS coverage by country.

What is payment initiation services (PIS)?

Payment Initiation Services (PIS) allow licensed providers—called PISPs (Payment Initiation Service Providers)—to initiate payments from a customer’s bank account to a payee via open banking APIs, with the customer’s consent. The payment is executed by the bank; the PISP does not hold funds. PIS enables account-to-account payments (e.g. SEPA, Faster Payments, ACH), often with instant or same-day settlement and lower fees than card schemes. Use cases include e-commerce checkout, bill pay, and person-to-person or business-to-business transfers. In the EU and UK, PISPs are regulated under PSD2 and the UK Open Banking Standard. Many open banking aggregators offer both AIS and PIS so that a single API can read accounts and initiate payments. The Open Banking Tracker lists aggregators by PIS support and geographic coverage.

PSD2 (Revised Payment Services Directive) is an EU directive that obliges banks in the European Economic Area to provide licensed third-party providers (TPPs) with access to customer accounts via dedicated APIs—with the customer’s consent—for account information (AIS) and payment initiation (PIS). It has been in force since 2018 and is implemented in each member state’s law. PSD2 created the legal basis for open banking in Europe: AISPs can access account data, and PISPs can initiate payments, without the TPP needing to be a bank. TPPs must be authorized or registered with a national competent authority and use strong customer authentication (SCA) where required. The UK retained equivalent requirements after Brexit under the UK Open Banking Standard. The Open Banking Tracker lists regulations by country and links to regulators and API directories.

What is open finance?

Open finance extends the concept of open banking beyond payment accounts to a broader set of financial data and products: savings, investments, pensions, insurance, and sometimes lending. The idea is the same—secure, API-based access for licensed third parties with customer consent—but applied across the financial ecosystem. In the EU, the proposed FIDA (Financial Data Access) regulation would create a framework for open finance, building on PSD2. The UK has been exploring open finance via the FCA and industry initiatives. Other regions are advancing similar concepts (e.g. Consumer Data Right in Australia). The Open Banking Tracker covers open banking and open finance regulations, standards, and providers globally. Our Open Finance page and Open Finance Map summarize regulations and adoption by region.

What is FDX and how does it relate to open banking?

FDX (Financial Data Exchange) is a US industry body that defines technical and security standards for sharing consumer and business financial data via APIs. FDX standards are used by many US banks, data aggregators, and fintechs to provide consent-based access to account and transaction data—similar in spirit to open banking in the UK and EU. Unlike PSD2 in Europe, the US does not have a single regulatory mandate requiring banks to offer APIs. FDX fills part of that gap by providing a common API specification (FDX API) and security model so that data can be shared in a standardized way when data holders and aggregators adopt it. The Open Banking Tracker tracks FDX adoption, US open banking initiatives, and API aggregators that support US banks. See our Data Standards and Open Banking API pages for more context.

Which API aggregators support UK open banking?

Several API aggregators support UK open banking via the UK Open Banking Standard. Prominent examples include TrueLayer, Tink, Yapily, Plaid, GoCardless, Token, Salt Edge, and Experian (among others). They offer a single API integration to multiple UK banks and building societies, for account information (AIS) and often payment initiation (PIS). UK open banking is mandated by the CMA order and implemented via the Open Banking Implementation Entity (OBIE). Aggregators connect to the standardised APIs provided by UK account providers. Coverage and product mix (AIS, PIS, premium APIs) vary by aggregator; some also offer European or global coverage. The Open Banking Tracker maintains a directory of API aggregators with filters by country (e.g. United Kingdom), product type (AIS/PIS), and sandbox availability. Use the API aggregators page to compare and find providers that support UK open banking.

Which API aggregators support European PSD2?

Numerous API aggregators support European PSD2 open banking across the EEA. Examples include Tink, TrueLayer, Yapily, Plaid, Token, Salt Edge, Banked, Nordigen (now GoCardless), and many others. They provide a single integration to banks in multiple EU/EEA countries for account information (AIS) and often payment initiation (PIS). PSD2 requires banks in the EEA to offer dedicated access to licensed AISPs and PISPs. Aggregators connect to these bank APIs (and sometimes to local standards such as Berlin Group) so that one integration can cover many countries. Coverage, bank list, and premium APIs vary by provider. The Open Banking Tracker directory lists API aggregators with filters by country (e.g. Germany, France, Netherlands) and by AIS/PIS. Use the API aggregators page to compare European PSD2 coverage.

Which API aggregators support US open banking?

In the US, open-banking-style data access is provided by data aggregators such as Plaid, MX, Yodlee (Envestnet), Finicity (Mastercard), Akoya, and others. They connect to thousands of US banks and credit unions, often via a mix of APIs (where banks or networks offer them) and secure data aggregation methods. FDX is increasingly used where supported. The US does not have a PSD2-style regulatory mandate, so coverage and technical approaches vary. Aggregators typically offer account aggregation (balances, transactions) and sometimes payment or transfer features. Developers integrate once to the aggregator and gain access to many institutions. The Open Banking Tracker lists API and data aggregators with US coverage. Use the API aggregators directory and filters to compare US open banking and financial data providers.

Which API aggregators offer a single API for multiple countries?

Several API aggregators offer a single API that covers multiple countries. Examples include Tink (broad European coverage and more), Plaid (US, Canada, UK, and Europe), TrueLayer (UK and Europe), Yapily (UK and Europe), Salt Edge (global), Token (Europe), and GoCardless (UK and Europe). Each provides one integration for developers while supporting many banks and markets. This “build once, connect everywhere” model reduces integration effort: you integrate to the aggregator’s API and then enable countries or banks via configuration. Coverage, product mix (AIS/PIS), and pricing vary; some focus on specific regions or use cases. The Open Banking Tracker directory lists API aggregators with country and region filters. Use the API aggregators page to compare multi-country coverage and choose a provider that supports your target markets.

Which open banking providers offer a sandbox?

Many open banking API aggregators and banks offer sandbox or test environments so developers can build and test without touching live accounts. Aggregators that commonly offer sandboxes include TrueLayer, Tink, Yapily, Plaid, GoCardless, Token, Salt Edge, and others. National schemes (e.g. UK Open Banking) also provide test environments for bank APIs. Sandboxes typically provide test credentials, mock accounts, and simulated flows for account information and payment initiation. This allows integration and compliance testing before going live. Availability and access (e.g. self-serve vs. request) vary by provider. The Open Banking Tracker lists sandbox availability for API aggregators and for individual banks where we have the data. Use the API aggregators directory and filter or column for “Sandbox” to find providers that offer a sandbox.

Which countries have open banking regulations?

Open banking or open finance regulations exist in a growing number of jurisdictions. The UK and EU/EEA have mandatory open banking (UK Open Banking Standard and PSD2). Australia has the Consumer Data Right (CDR). Brazil has open finance (Banco Central). Mexico, Canada, India, Singapore, Hong Kong, Japan, and others have either mandates or industry-led initiatives. The US is moving toward broader data sharing (e.g. FDX, CFPB rulemaking) without a single PSD2-style mandate. The Open Banking Tracker tracks open banking and open finance regulations worldwide. Our Open Banking Regulations page and Open Finance Map list countries and frameworks, with links to regulators and key standards. Coverage includes Europe, Americas, APAC, and Middle East. For a visual overview of which countries have regulations and their status, see the Open Finance Map. For detailed regulation pages (scope, timeline, APIs), use the Regulations section.

Who regulates open banking in the UK?

Open banking in the UK is regulated and overseen by the Financial Conduct Authority (FCA) and the Competition and Markets Authority (CMA). The FCA authorizes or registers payment service providers, including AISPs and PISPs that use open banking APIs. The CMA’s retail banking market order required the nine largest banks to implement open banking and established the Open Banking Implementation Entity (OBIE) to develop and maintain the UK Open Banking Standard. The OBIE (now transitioning to the Open Banking Limited entity) has been responsible for the technical standards, security, and directory used by UK account providers and TPPs. Day-to-day supervision of TPPs and enforcement sit with the FCA. The Open Banking Tracker lists the UK under Open Banking Regulations with links to the FCA and CMA.

Who regulates open banking in the EU?

Open banking in the EU is governed by PSD2 (Revised Payment Services Directive), implemented in each member state’s national law. Supervision is carried out by the national competent authority (NCA) in each country—for example, BaFin in Germany, ACPR/AMF in France, and the Central Bank of the Netherlands (DNB) in the Netherlands. These authorities authorize or register payment institutions and e-money institutions that act as AISPs and PISPs. The European Banking Authority (EBA) issues guidelines and regulatory technical standards that support a consistent application of PSD2 across the EU. TPPs are typically authorized in one member state and can passport their services across the EEA. The Open Banking Tracker lists EU countries and their regulators in the Regulators and Open Banking Regulations sections.

What is the UK Open Banking Standard?

The UK Open Banking Standard is the technical and operational framework that defines how banks and building societies in the UK expose account and payment APIs to licensed third-party providers. It was created under the CMA’s retail banking market order and developed and maintained by the Open Banking Implementation Entity (OBIE). It covers account information (AIS) and payment initiation (PIS), including security, consent, and customer experience requirements. The standard ensures a consistent API design and security model across the largest UK account providers, so TPPs can integrate once and connect to multiple banks. It has been a major driver of open banking adoption in the UK. The Open Banking Tracker covers the UK under Open Banking Regulations and links to the official standard and directory.

How do I integrate an open banking API?

To integrate an open banking API, you typically: (1) choose an API aggregator or connect directly to a bank’s API if you only need one bank; (2) register for API credentials and, if offered, a sandbox; (3) implement the authorization flow (usually OAuth 2.0 or similar) so users can consent to sharing their accounts; (4) call the aggregator’s or bank’s endpoints for account list, balances, transactions, and optionally payment initiation; (5) handle errors, consent expiry, and re-authentication; and (6) test in sandbox then go live with production credentials. Most teams integrate via an aggregator (e.g. TrueLayer, Tink, Plaid, Yapily) so one integration covers many banks. Aggregators provide SDKs, docs, and sandboxes. You’ll need to comply with local regulations (e.g. PSD2 in the EU, FCA in the UK) if you’re the regulated entity, or rely on the aggregator’s license where applicable. The Open Banking Tracker lists API aggregators with sandbox info and links to developer portals. Our guides (e.g. Open Banking API Integration) and Open Banking API page explain concepts and integration steps in more detail.

Which banks offer open banking APIs in the UK?

In the UK, the nine banks and building societies covered by the CMA order (e.g. Barclays, HSBC, Lloyds, NatWest, Santander UK, and others) are required to offer open banking APIs. Many additional UK banks and building societies have joined voluntarily, so a large share of UK current accounts are accessible via the UK Open Banking Standard. Access is typically through the standardised APIs defined by the Open Banking Implementation Entity. Third parties connect either directly to each bank’s API or via an API aggregator (e.g. TrueLayer, Yapily, Tink) that connects to many UK banks through one integration. The Open Banking Tracker provider directory lists UK banks and their API and aggregator coverage. Use the Open Banking Tracker to browse providers by country (United Kingdom) and see which banks support open banking, which aggregators connect to them, and links to developer portals where available.

What is the difference between AIS and PIS in open banking?

In open banking, AIS (Account Information Services) and PIS (Payment Initiation Services) are the two main service types. AIS allows a licensed provider (AISP) to access a customer’s account data—balances and transactions—via APIs with the customer’s consent. It is read-only: no money is moved. PIS allows a licensed provider (PISP) to initiate a payment from the customer’s account to a payee, again with consent. The bank executes the payment; the PISP does not hold funds. AIS is used for account aggregation, affordability checks, budgeting, and accounting integrations. PIS is used for instant checkout, bill pay, and account-to-account transfers. Many API aggregators offer both so that one integration can support “read accounts” and “initiate payments” use cases. Under PSD2 and the UK Open Banking Standard, banks must support both AIS and PIS access for licensed TPPs. The Open Banking Tracker glossary defines AIS, PIS, AISP, and PISP in more detail. The API aggregators directory lets you filter by AIS and PIS support.

How does open banking differ from PSD2?

Open banking is the broader concept: securely sharing bank account data with third-party providers through APIs, with the customer's consent. PSD2 (Revised Payment Services Directive) is the EU legislation that implements and regulates open banking in the European Economic Area. So PSD2 is one way—the EU way—of doing open banking; open banking itself is global and can be driven by other regulations (e.g. UK Open Banking Standard) or industry standards (e.g. FDX in the US). Under PSD2, banks in the EEA must provide dedicated access to licensed AISPs and PISPs. The UK kept equivalent requirements after Brexit. Other regions (Australia, Brazil, etc.) have their own open banking or open finance frameworks. The Open Banking Tracker covers both PSD2 and other open banking regulations worldwide.

Is my data safe with open banking?

Open banking is designed to be safe: you give explicit consent before any data is shared, and only licensed or registered third-party providers (TPPs) can access your account data. They connect via dedicated APIs—you do not share your online banking username and password with the TPP. Banks and TPPs must follow strong customer authentication (SCA) and data protection rules (e.g. GDPR in the EU). Regulators (e.g. FCA in the UK, national authorities in the EU) supervise TPPs. You can revoke consent at any time. The Open Banking Tracker lists regulated aggregators and links to official directories (e.g. UK Open Banking) where you can verify that a provider is authorized.

How can open banking help businesses?

Open banking helps businesses in several ways: (1) Onboarding and verification—using bank data to verify identity and income without manual statements. (2) Lending and affordability—assessing cash flow and risk via account and transaction data. (3) Account aggregation—viewing multiple business accounts in one dashboard. (4) Pay-by-bank—accepting or making account-to-account payments with lower fees than cards. (5) Accounting and reconciliation—feeding transaction data into ERP and accounting systems automatically. API aggregators give businesses a single integration to many banks for these use cases. The Open Banking Tracker lists aggregators by country and product (AIS, PIS) so you can compare providers for business use.

What is the difference between Plaid and TrueLayer?

Plaid is strongest in North America (US and Canada) and is widely used for account linking, transaction data, income verification, and identity signals. It also offers UK and European coverage. TrueLayer is UK- and Europe-focused and is often chosen for payment initiation (pay-by-bank, instant bank-to-bank payments) as well as account information. Both offer a single API to many banks. Choose Plaid if your primary market is the US or Canada or you need deep data and verification features; choose TrueLayer if you are building in the UK or Europe and need strong pay-by-bank or a payments-first API. The Open Banking Tracker compares API aggregators by country and product type (AIS/PIS) so you can evaluate both and others.

What is open banking used for?

Open banking is used for: (1) Account aggregation—showing multiple bank accounts in one app. (2) Income and affordability checks—lenders and landlords verifying income and spending. (3) Pay-by-bank—checkout and transfers via instant bank-to-bank payments. (4) Budgeting and categorization—apps that read transactions and categorize spending. (5) Accounting and ERP—automated bank feeds into Xero, QuickBooks, and other systems. (6) Identity and verification—using bank-held data to verify identity or account ownership. These use cases are powered by account information (AIS) and payment initiation (PIS) APIs. The Open Banking Tracker lists use cases, API aggregators, and which banks support open banking in each country.

Do I need a license to use open banking APIs?

It depends who is accessing the data or initiating payments. If your company is directly accessing customers' bank accounts or initiating payments on their behalf, you generally need to be an authorized or registered AISP and/or PISP (or equivalent under local law). If you integrate via an API aggregator (e.g. Plaid, TrueLayer, Tink, Yapily), the aggregator holds the license and you use their API under their terms—you do not need your own payment-services license for that integration. Regulations differ by country (e.g. FCA in the UK, national authorities in the EU under PSD2). The Open Banking Tracker lists regulated aggregators and links to regulator directories so you can confirm licensing and decide whether to become a TPP or use an aggregator.

Which open banking provider is best for payments?

For payment initiation (pay-by-bank, instant bank-to-bank): TrueLayer and GoCardless are often chosen in the UK and Europe; Tink and Yapily also offer strong PIS coverage in the EU. In the US, Plaid and other aggregators offer account-to-account or transfer-style products. 'Best' depends on your target country, bank coverage, and whether you need one-off payments, recurring payments, or payouts. The Open Banking Tracker API aggregators directory lets you filter by PIS (payment initiation) support and by country so you can compare providers for your payments use case.

Is open banking mandatory for banks?

In the UK and in the EU/EEA, open banking is mandatory for in-scope banks. In the UK, the CMA order requires the nine largest banks and building societies to implement the UK Open Banking Standard; many others have joined voluntarily. In the EU, PSD2 requires banks to offer dedicated access to licensed AISPs and PISPs. In the US, there is no single PSD2-style mandate yet; many banks participate via data aggregators and standards like FDX voluntarily or under emerging rules. The Open Banking Tracker lists which countries have open banking regulations and links to regulators and implementation bodies.

What is strong customer authentication (SCA) in open banking?

Strong customer authentication (SCA) is a requirement under PSD2 in the EU and in the UK: when a customer initiates a payment or grants access to account data, the process must use at least two independent factors—typically something you know (e.g. password), something you have (e.g. phone or token), and/or something you are (e.g. biometric). This reduces fraud and unauthorized access. In open banking, SCA is applied during the consent and authorization flow (e.g. when the user is redirected to their bank to approve access). Banks and TPPs must comply with SCA rules; API aggregators handle the technical flow. The Open Banking Tracker glossary and regulation pages cover SCA in more detail.

What is Banking as a Service (BaaS)?

Banking as a Service (BaaS) is a model where licensed banks expose their core banking infrastructure—accounts, payments, cards, lending, and compliance—via APIs so that non-bank companies can embed financial products directly into their own platforms. The bank holds the license and handles regulatory requirements; the BaaS client builds the customer-facing experience. BaaS enables use cases such as branded debit cards inside a gig-economy app, embedded lending at point of sale, or IBAN accounts inside an accounting tool—without the non-bank needing its own banking license. Providers in this space include Solaris, ClearBank, Railsr, Griffin, and others. Some embedded finance platforms bundle BaaS with card issuing, compliance tooling, and ledger services. The Open Banking Tracker lists BaaS and embedded finance providers with filters by capability (accounts, cards, lending, payments) and geography. See the Embedded Finance directory to compare platforms.

What can open banking see?

When you give consent, open banking allows a licensed third-party provider to see specific data from the accounts you authorise: typically your account holder name, account number and sort code, current balance, and transaction history (dates, amounts, descriptions, and counterparties). The exact data depends on the provider's permissions (AIS scope) and the regulation in your country. Open banking cannot see accounts you have not consented to share, your online banking password or card PIN, or data from other financial products (e.g. pensions, insurance) unless the regulation explicitly covers them (as open finance frameworks may in the future). You can revoke consent at any time through your bank or the third-party app, and consent typically expires after 90 days under PSD2/UK Open Banking rules unless you re-authorise. The Open Banking Tracker explains AIS (Account Information Services) data scope in more detail. For provider-level privacy and security information, see individual aggregator pages in the API aggregators directory.

What is screen scraping in banking?

Screen scraping in banking is a technique where a third-party application uses the customer's online banking username and password to log in on their behalf, then extracts (scrapes) account data—balances, transactions, account details—from the bank's web interface. It was the primary method used by early data aggregators (e.g. Yodlee, Plaid in earlier years) before dedicated APIs existed. Screen scraping carries significant risks: the customer shares their banking credentials with a third party, there is no standardised consent mechanism, and it can break when the bank changes its website. Open banking regulations such as PSD2 in the EU and the UK Open Banking Standard were designed to replace screen scraping with secure, API-based access where the customer authorises data sharing directly with their bank without revealing credentials. Some markets (notably the US) still rely partly on credential-based access alongside emerging API standards like FDX. The Open Banking Tracker tracks which countries and aggregators have moved from screen scraping to API-based access.

What is a Variable Recurring Payment (VRP)?

A Variable Recurring Payment (VRP) is an open banking payment instruction where the customer authorises a third-party provider to initiate multiple future payments from their bank account, with amounts and timing that can vary within agreed limits. The customer consents once (setting parameters such as maximum per-payment amount, maximum cumulative amount, and frequency), and subsequent payments execute automatically without requiring re-authentication each time. VRPs are often described as the open-banking successor to direct debits: they offer real-time settlement, granular customer control, and lower fees. The UK was first to mandate VRP for sweeping use cases (moving money between a customer's own accounts), and commercial VRP for paying third parties (e.g. subscriptions, utility bills) is being rolled out. The EU is exploring similar functionality under PSD3/PSR. The Open Banking Tracker covers VRP-capable aggregators and payment initiation providers. See the Payment Initiation Services page and glossary for more on VRP, sweeping, and non-sweeping use cases.

Open Banking Q&A – Answers from Open Banking Tracker

Each page answers one question in plain language. Use these for research, integration planning, or when you need a citable source for open banking, APIs, and regulations.

What is an open banking API?
What is an AISP?
What is a PISP?
What is account information services (AIS)?
What is payment initiation services (PIS)?
What is PSD2?
What is open finance?
What is FDX and how does it relate to open banking?
Which API aggregators support UK open banking?
Which API aggregators support European PSD2?
Which API aggregators support US open banking?
Which API aggregators offer a single API for multiple countries?
Which open banking providers offer a sandbox?
Which countries have open banking regulations?
Who regulates open banking in the UK?
Who regulates open banking in the EU?
What is the UK Open Banking Standard?
How do I integrate an open banking API?
Which banks offer open banking APIs in the UK?
What is the difference between AIS and PIS in open banking?
How does open banking differ from PSD2?
Is my data safe with open banking?
How can open banking help businesses?
What is the difference between Plaid and TrueLayer?
What is open banking used for?
Do I need a license to use open banking APIs?
Which open banking provider is best for payments?
Is open banking mandatory for banks?
What is strong customer authentication (SCA) in open banking?
What is Banking as a Service (BaaS)?
What can open banking see?
What is screen scraping in banking?
What is a Variable Recurring Payment (VRP)?

Explore further

Compare API aggregators, read the Open Banking API guide, or browse regulations by country.

API aggregators →Open Banking API guide →Regulations →Glossary →

Open Banking Q&A

Clear answers to questions about open banking APIs, aggregators, regulations, and integration. Built for humans and AI.

Explore further

Compare Open Banking API Providers

Want to integrate Accounting & ERP data?