Skip to main content

Data Insights

Data Insights is the dashboard area of the Embedder Portal where you explore aggregate metrics about your programmeProgramme A programme represents your application within Weavr. Everything you create — Identities, Instruments, Transactions — sits beneath a Programme. When you register as an Embedder, you receive a Programme in the Sandbox and, once approved, one in Production.. It gives you near real-time views of identity onboarding, transaction activity, authentication events, and API usage — built to answer day-to-day operational questions without writing reports against the API.

You reach Data Insights from the Insights entry in the Portal navigation, or directly at portal.weavr.io/insights. Dashboards are available on both Sandbox and Live, with each environment showing its own data.

Layout​

Data Insights is organized into top-level tabs, each grouping the dashboards related to one area of activity:

  • Identities — identity onboarding and KYBKYB Know Your Business - the identity verification process for corporate identities. This process allows you to seamlessly and securely verify your business customer's identity. Weavr will ask users to submit the necessary information and documentation so that they can get approved by financial providers. activity.
  • Transactions — funds moving in and out of your programmeProgramme A programme represents your application within Weavr. Everything you create — Identities, Instruments, Transactions — sits beneath a Programme. When you register as an Embedder, you receive a Programme in the Sandbox and, once approved, one in Production., including card and account activity.
  • Payment RunsPayment Run A list of payments created by Buyers to settle their outstanding financial obligations with their suppliers. Payment runs are typically managed by the accounts payable function within a business on a periodic basis and go through stages of creation, authorisation, funding, and execution. — Payment RunPayment Run A list of payments created by Buyers to settle their outstanding financial obligations with their suppliers. Payment runs are typically managed by the accounts payable function within a business on a periodic basis and go through stages of creation, authorisation, funding, and execution. activity, where the programmeProgramme A programme represents your application within Weavr. Everything you create — Identities, Instruments, Transactions — sits beneath a Programme. When you register as an Embedder, you receive a Programme in the Sandbox and, once approved, one in Production. uses Payment RunPayment Run A list of payments created by Buyers to settle their outstanding financial obligations with their suppliers. Payment runs are typically managed by the accounts payable function within a business on a periodic basis and go through stages of creation, authorisation, funding, and execution..
  • Authentication — SCASCA Strong Customer Authentication - a two-factor authentication solution required by PSD2 regulations for when end-users are accessing their payment account sensitive information or initiating transactions. SCA requires at least two of the following: something you know (password), something you have (device), or something you are (biometrics). and step-up authentication events.
  • Technical — API calls and other technical activity at the integration layer.

Each tab contains one or more dashboards. The exact set evolves over time as we add new views, and the dashboards available to you also depend on your programmeProgramme A programme represents your application within Weavr. Everything you create — Identities, Instruments, Transactions — sits beneath a Programme. When you register as an Embedder, you receive a Programme in the Sandbox and, once approved, one in Production. configuration. For the canonical, up-to-date list, see Dashboard catalog.

Dashboard structure​

Each dashboard typically exposes three views:

  • Overview — high-level KPIs and daily trends, usually for the last 30 days.
  • Analysis — charts that let you slice the data by status, identity, currency, or other dimensions.
  • Details — a granular table at identity, instrumentInstrument A financial product owned by an Identity. There are two types: Managed Accounts (stored-value accounts that hold balances and can receive wire transfers) and Managed Cards (prepaid cards — virtual or physical — used for purchases)., or transaction level. Use this to drill from an aggregate number to the individual record.

Filters appear at the top of each dashboard. The most common filters are time range, identity, currency, and status, and they apply across the Overview, Analysis, and Details views simultaneously. Hover any chart to see a tooltip describing what it measures and at what granularity.

Sandbox and live data​

In Sandbox, dashboards reflect the synthetic data you create through your integration and through the Simulator. Use them to validate that your test flows produce the metrics you expect before moving to Live.

In Live, dashboards reflect real customer activity and update in near real-time. Treat them as your operational view alongside the Console — the Console shows the per-record state, Data Insights shows the aggregate.

Dashboard catalog​

For the canonical list of dashboards currently available, including descriptions of every chart and the filters each one supports, see the Data Insights knowledge base on the Weavr support portal. The Help button inside the Embedder PortalEmbedder Portal A web-based portal where embedders can access their Weavr account, manage API credentials, configure settings, view dashboards, and access documentation. The portal provides access to both sandbox and production environments, with separate credentials for each. links to the same articles.

Next steps​

  • Console — drill from an aggregate metric to an individual identity, instrumentInstrument A financial product owned by an Identity. There are two types: Managed Accounts (stored-value accounts that hold balances and can receive wire transfers) and Managed Cards (prepaid cards — virtual or physical — used for purchases)., or transaction.
  • Simulator — generate Sandbox activity that shows up in your dashboards.
  • Webhook logs — see the underlying events that drive transaction and authentication metrics.