Quick Guide

Disclaimer

Fliqa's platform is exclusively designed for corporate or business use and is not intended for individual or personal use!

This page is a fast, end-to-end overview of onboarding onto Fliqa and integrating Payment Initiation (PIS) and Account Information (AIS). Use it as a map — every section links to the full documentation for details.

1. What Fliqa does

Fliqa lets you connect to many open banking providers (banks) through a single API. Integrate once with Fliqa and get:

• Payment Initiation — let customers pay you directly from their bank account.
• Account Information — with the customer's consent, read account ownership, balances and transactions.

See How Open Banking Works and Bank / provider flows (redirect, embedded, decoupled) for background.

2. Create an account and configure your tenant

1. Sign up and register your company — you're immediately granted Sandbox (Demo) access.
2. Configure the following in the Fliqa portal before testing:

Configuration	Purpose	Required for
Tenant info	Public-facing name/description shown on customer dialogs	Sandbox & Production
Company info	Legal business information for onboarding and dialogs	Production (mandatory)
Contacts	Company contacts plus business owners/UBOs for KYB/KYC	Production (mandatory)
Services	Enable Payments, Account information and/or Credit scoring	Production access scope
Point of Sale	IBAN account that receives payments	Payments only
Account inquiry	Scope and frequency of account access requested	Account information only

Company info and business owner details are shared between Sandbox and Production and are mandatory before going live.

3. Authenticate

Exchange your Api-Key / Api-Secret pair for a short-lived Bearer access token, scoped per environment and per flow:

GET /payment/auth/token/{environment}/{channel}/{pointOfSaleId}
GET /account/auth/token/{environment}/{channel}/{inquiryId}

Best practice: mint the token on your backend and hand it to the dialog via the accessTokenGet callback so your Api-Secret never reaches the browser. Full reference: API Settings — keys, domains, webhooks.

4. Choose how to integrate

• Hosted dialog (recommended) — drop in a JavaScript component; Fliqa renders bank selection and confirmation, and handles desktop → mobile handoff. Covers both payments and account information.
• Direct API — call the REST endpoints yourself for full UI control. See the Payments API flow and Account information API flow.
• Pay by Link — a link or QR code that opens the payment dialog full-screen.
• Plugins — no-code e-commerce plugins (e.g. WooCommerce) adding a "Bank Account" payment method at checkout.

Minimal hosted payment dialog

<script src="https://assets.fliqa.io/sdk/latest/fliqaComponent.js"></script>

<button onclick="executePayment()">Pay with bank account</button>
<script>
  function executePayment() {
    fliqaComponent().then(fliqa => {
      fliqa.pay({
        production: false, // false in sandbox
        accessTokenGet: getAccessToken,
        data: {
          payment: {
            pointOfSaleId: "<point_of_sale_id>",
            name: "<transaction_name>",
            description: "<transaction_desc>",
            amount: 12.50,
            currency: "EUR"
          }
        }
      });
    });
  }
</script>

5. Handle webhooks

Register webhook endpoints per service and environment to receive final payment and consent status events. Endpoints must accept POST over HTTPS and return 200 OK immediately. Verify authenticity using the X-Fliqa-Signature header. Details: Webhooks and signature verification.

6. Test in the Sandbox

All sandbox banks are simulated — same behavior as production, no live bank data. Use the provided test providers to exercise accepted and rejected outcomes across redirect, embedded and decoupled flows before moving on.

7. Go to production

Once your sandbox integration works end-to-end:

1. Complete onboarding — KYB/KYC checks, contract signing.
2. Create production API keys (separate from sandbox) and configure production allowed domains and webhooks.
3. Have Fliqa approve your Points of Sale (required in production).
4. Switch the API environment to production (or set production: true / omit it in the dialog) and use the production keys.

8. Error handling

Errors share a common schema: errorMessage, errorCode, an optional errorSubCode, plus documentationUrl, requestId and resourceId. See the Unauthorized, Bad request and Not found error references for common codes and causes.

---

Next steps: work through the Getting started section in order — Tenant info → Company info → Point of Sale / Account inquiry — then try the Sandbox.