Nexio connector
Set up the Nexio connector in Kaivo: authentication, configuration, the 6 BigQuery tables it syncs, and answers to common questions.
Nexio connector pricing, tier and credits on kaivo.io
Kaivo is a fully managed data platform that syncs your Nexio data into a Google BigQuery warehouse and keeps it up to date automatically. There is no pipeline to build and no infrastructure to run, so you can spend your time analysing your payment and finance data instead of moving it.
What is the Nexio connector
Section titled “What is the Nexio connector”Sync your Nexiopay payments data into BigQuery with Kaivo to analyse transactions alongside the rest of your finance data.
| Category | Finance & Payments |
|---|---|
| Authentication | API key |
| Setup | Self-service |
Getting started with the Nexio connector
Section titled “Getting started with the Nexio connector”- Sign up for Kaivo and create a workspace.
- Connect your Nexio account.
- Choose which tables to sync.
- Wait for the initial sync to finish.
- Query your data in BigQuery or your favourite AI or BI tool.
Authenticating Nexio
Section titled “Authenticating Nexio”Authenticate with your API Key.
| Field | Description |
|---|---|
| API Key | |
| Your Nexio API key (password). You can find it in the Nexio Dashboard under Settings > User Management. Select the API user and copy the API key. |
|
Configuring the Nexio connector
Section titled “Configuring the Nexio connector”When you set up the connector, you provide:
| Field | Description |
|---|---|
| API Username | |
| Your Nexio API username. You can find it in the Nexio Dashboard under Settings > User Management. Select the API user and copy the username. |
| | Subdomain |
The subdomain for the Nexio API environment, such as ‘nexiopaysandbox’ or ‘nexiopay’.
| | Start Date |
Any data before this date will not be fetched.
|
Tables and columns synced from Nexio
Section titled “Tables and columns synced from Nexio”Kaivo syncs 6 tables from Nexio into a dedicated dataset in your BigQuery warehouse. Click any table to see its columns and types.
card_tokens (15 columns)
| Column | Type | Description |
|---|---|---|
_kaivo_id |
STRING |
Primary key that uniquely identifies the row. Auto-generated by Kaivo. |
account_updater_status |
STRING |
|
card_holder_name |
STRING |
|
created_at |
STRING |
|
expiration_month |
FLOAT64 |
|
expiration_year |
FLOAT64 |
|
first_six |
STRING |
|
key |
STRING |
|
last_four |
STRING |
|
merchant_id |
STRING |
|
pause_account_updater |
BOOL |
|
should_update_card |
BOOL |
|
token |
STRING |
|
updated_at |
STRING |
|
_kaivo_extracted_at |
TIMESTAMP |
Timestamp that shows when the row was extracted. Auto-generated by Kaivo. |
payment_types (4 columns)
| Column | Type | Description |
|---|---|---|
_kaivo_id |
STRING |
Primary key that uniquely identifies the row. Auto-generated by Kaivo. |
id |
FLOAT64 |
|
name |
STRING |
|
_kaivo_extracted_at |
TIMESTAMP |
Timestamp that shows when the row was extracted. Auto-generated by Kaivo. |
recipients (15 columns)
| Column | Type | Description |
|---|---|---|
_kaivo_id |
STRING |
Primary key that uniquely identifies the row. Auto-generated by Kaivo. |
country |
STRING |
|
created_at |
STRING |
|
email |
STRING |
|
first_name |
STRING |
|
last_name |
STRING |
|
payout_account_id |
FLOAT64 |
|
provider_id |
FLOAT64 |
|
provider_recipient_ref |
STRING |
|
provider_type |
FLOAT64 |
|
recipient_id |
FLOAT64 |
|
recipient_ref |
STRING |
|
updated_at |
STRING |
|
user_type |
STRING |
|
_kaivo_extracted_at |
TIMESTAMP |
Timestamp that shows when the row was extracted. Auto-generated by Kaivo. |
spendbacks (17 columns)
| Column | Type | Description |
|---|---|---|
_kaivo_id |
STRING |
Primary key that uniquely identifies the row. Auto-generated by Kaivo. |
amount |
FLOAT64 |
|
created_at |
STRING |
|
currency |
STRING |
|
id |
FLOAT64 |
|
payout_account_id |
FLOAT64 |
|
provider_id |
FLOAT64 |
|
provider_spendback_ref |
STRING |
|
provider_type |
FLOAT64 |
|
recipient_id |
FLOAT64 |
|
recipient_ref |
STRING |
|
spendback_date |
STRING |
|
spendback_ref |
STRING |
|
spendback_status |
FLOAT64 |
|
spendback_type |
FLOAT64 |
|
updated_at |
STRING |
|
_kaivo_extracted_at |
TIMESTAMP |
Timestamp that shows when the row was extracted. Auto-generated by Kaivo. |
terminal_list (13 columns)
| Column | Type | Description |
|---|---|---|
_kaivo_id |
STRING |
Primary key that uniquely identifies the row. Auto-generated by Kaivo. |
device_id |
STRING |
|
gateway_label |
STRING |
|
gateway_name |
STRING |
|
gateway_type |
FLOAT64 |
|
merchant_id |
STRING |
|
merchant_name |
STRING |
|
terminal_id |
STRING |
|
terminal_key |
STRING |
|
terminal_name |
STRING |
|
terminal_serial_number |
STRING |
|
terminal_status |
STRING |
|
_kaivo_extracted_at |
TIMESTAMP |
Timestamp that shows when the row was extracted. Auto-generated by Kaivo. |
user (17 columns)
| Column | Type | Description |
|---|---|---|
_kaivo_id |
STRING |
Primary key that uniquely identifies the row. Auto-generated by Kaivo. |
access_rights__merchant_ids___332221 |
STRING |
|
access_rights__role |
STRING |
|
account_id |
STRING |
|
account_type |
STRING |
|
cognito_sub |
STRING |
|
date_created |
STRING |
|
date_last_modified |
STRING |
|
enabled |
BOOL |
|
is_api_user |
BOOL |
|
is_enabled_for_account_updater |
BOOL |
|
is_enabled_for_cybersource_account_updater |
BOOL |
|
is_enabled_for_v_term |
BOOL |
|
payout_access_rights___5045 |
STRING |
|
random_1569849 |
STRING |
|
user_name |
STRING |
|
_kaivo_extracted_at |
TIMESTAMP |
Timestamp that shows when the row was extracted. Auto-generated by Kaivo. |
How the Nexio sync works
Section titled “How the Nexio sync works”After the first load, Kaivo keeps your BigQuery warehouse up to date for you. Where Nexio supports it, each sync pulls only new and changed records so it stays fast; otherwise it refreshes the whole table. Every record keeps its original ID, so you won’t get duplicate rows.
Frequently asked questions
Section titled “Frequently asked questions”How long does the initial sync take for Nexio?
Section titled “How long does the initial sync take for Nexio?”It depends on how much history is in your Nexio account. Most initial syncs finish within minutes, while large accounts can take a few hours. After that, syncs only fetch new and changed records, so they’re much faster.
Can I sync only some tables or columns?
Section titled “Can I sync only some tables or columns?”Yes. You pick which tables to sync when you set up the connection and can change the selection later. Tables you don’t select are never copied to your warehouse.
What happens when Nexio’s schema changes?
Section titled “What happens when Nexio’s schema changes?”New fields are never added automatically. You choose which fields to sync, so data you haven’t selected (sensitive personal data, for example) never lands in your warehouse. When a new field appears, it becomes available for you to add. What happens to removed or renamed fields depends on a table’s sync mode: full-refresh tables always match what’s currently in Nexio, so dropped fields disappear, while incremental tables keep their existing columns and history, so an old field stays and newly added fields fill in over time.
How do I handle GDPR or data deletion requests?
Section titled “How do I handle GDPR or data deletion requests?”Your data lives in your own Kaivo-managed BigQuery warehouse, so the most direct option is to delete or anonymise specific records right in BigQuery. If you delete data in Nexio instead, full-refresh tables drop it on the next sync, while incremental tables keep it, so you would remove the row in BigQuery or ask us to run a full refresh. To remove everything, delete the Nexio connector in Kaivo and all of its synced data is deleted with it.
Common use cases for Nexio data
Section titled “Common use cases for Nexio data”Payment reporting
Section titled “Payment reporting”Use payment_types and card_tokens to track payment volume and methods over time.
Recipient view
Section titled “Recipient view”Use recipients and spendbacks to follow where money moves.
Terminal analysis
Section titled “Terminal analysis”Use terminal_list to compare activity across terminals.
Use Nexio data in your AI and BI tools
Section titled “Use Nexio data in your AI and BI tools”Once Nexio data lands in your Kaivo-managed BigQuery warehouse, you can explore it with AI tools or any BI tool that connects to BigQuery. Here’s how the most common destinations work with Nexio data.
Claude
Section titled “Claude”Use Kaivo’s MCP server to give Claude secure, workspace-scoped access to your data. Setup guide →
Power BI
Section titled “Power BI”Microsoft’s BI tool with a native BigQuery connector. Supports direct query and scheduled refresh. Setup guide →
Data Studio
Section titled “Data Studio”Free Google BI tool with native BigQuery support. One-click connection to your Kaivo warehouse; great for SMB teams on Google Workspace. Setup guide →
Tableau
Section titled “Tableau”The premium analytics standard, with native BigQuery integration. Setup guide →
Google Sheets
Section titled “Google Sheets”Use Connected Sheets to query BigQuery directly from a spreadsheet, with no SQL. Setup guide →
Connect via Power Query’s BigQuery connector. Setup guide →
Metabase
Section titled “Metabase”Open-source BI tool with strong BigQuery support. Setup guide →
See our pricing page for Nexio connector pricing and plan details.
Related connectors
Section titled “Related connectors”- Chargebee: Sync Chargebee to BigQuery.
- ChartMogul: Sync ChartMogul to BigQuery.
- Fennoa: Sync Fennoa to BigQuery.
- Fortnox: Sync Fortnox to BigQuery.
- FreshBooks: Sync FreshBooks to BigQuery.
- PayPal Enterprise Payments: Sync PayPal Enterprise Payments to BigQuery.