Skip to main content

What is Wych Data?

Wych Data is an accredited platform that helps you securely access consumer-consented data, including banking and energy datasets, and integrate those capabilities into your products.

You can use Wych to:

  • connect customers to their data providers (for example banks and energy retailers)
  • request and manage consent in a compliant way
  • retrieve data via APIs
  • optionally use pre-built insights and reports to reduce implementation effort

What can I build with Wych?

Use the APIs to retrieve raw and Wych-enhanced representations of data, suitable for teams that want maximum control over data handling, security, and downstream processing.

tip

Best for: product and engineering teams integrating into existing systems.

How it works

Wych follows a simple flow:

  1. Authenticate your application to the Wych API.
  2. Request consent from the customer using either the hosted journey or your own journey.
  3. Retrieve data using a customer (user context) token.
Key point

In an open banking flow, the customer authenticates directly with their bank or provider. Your application does not collect the customer’s banking credentials.

Use Wych’s compliant, brandable consent journey and direct customers to your app-specific connection link.

Use this when: you want the fastest path to production with minimal implementation effort.

Embed the consent journey into your existing application using Wych APIs. This is typically used for migrations or where you need a consistent cross-region experience.

Use this when: you have a strong CX and compliance capability and need full UI control.

Advanced integration

“Bring your own consent” journeys typically require additional review before production use.

Getting started

  1. Create your Wych account and sign in to the partner portal.
  2. Configure your partner profile (business details, branding, environments).
  3. Register your application (purpose, consent settings, callback URLs).
  4. Prepare access credentials (API key and tokens).
  5. Run your first connection (hosted or custom journey).
  6. Retrieve customer data (accounts, balances, transactions, and more).

Suggested next pages

  • Access credentials (API key and tokens)
  • Consent overview
  • Hosted consent journey (basic)
  • Bring your own consent journey (advanced)
  • Retrieve customer data