Release Notes

July 2025

We have added a new column, processed_with_network_token, to the TRANSACTION table. This column indicates whether the transaction was processed using a network token.

June 2025

We've added the following columns to the ANDROID_PAY_DETAILS table:

• commercial
• country_of_issuance
• debit
• healthcare
• issuing_bank
• payroll
• prepaid

We've added the following columns to the APPLE_PAY_CARD table:

• bin
• commercial
• country_of_issuance
• debit
• healthcare
• issuing_bank
• payroll
• prepaid

We have added the risk_data_transaction_risk_score column to the TRANSACTION and CREDIT_CARD_VERIFICATION tables.

We have also added a new table, DECISION_REASON, to sync decision_reasons with the risk_data_id.

We will gradually roll out this feature to all connections.

May 2025

We have changed the sync strategy for the following tables:

• SUBSCRIPTION
• SUBSCRIPTION_ADD_ON
• SUBSCRIPTION_DISCOUNT
• SUBSCRIPTION_STATUS_HISTORY

We now incrementally sync them to capture new records and re-import them on a scheduled basis to capture updates and deletes. The re-import frequency depends on the duration of the last re-import:

• If the last re-import took less than 2 hours, we re-import the table once a day.
• If the last re-import took more than 2 hours, we re-import the table once a week on Saturdays.

We are gradually rolling out these changes to all existing connections.

February 2025

We have upgraded our Braintree connector from version 3.29.0 to 3.39.0 of the Braintree API. For more information about the changes and deprecations, see Braintree API's changelog.

November 2024

We have added two new columns, billing_period_start_date and billing_period_end_date, to the TRANSACTION table. We are gradually rolling out this change to all existing connections. Until the change is available for your connections, you may observe these columns as null in your destination table.
If you want to re-sync the table and backfill the historical data for these columns, contact our Support team.

July 2024

We have upgraded our Braintree connector from version 3.19.0 to 3.29.0 of the Braintree API. For more information about the changes and deprecations, see Braintree API's changelog.

June 2024

We have changed our sync strategy for the DISPUTE table. To avoid data discrepancy, we now sync the past 3 days' data for this table daily. Previously, we only synced data for the past 2 days.

February 2024

The Braintree connector now supports priority-first sync. Priority-first syncs fetch your most recent data first so that it's quickly ready for you to use. Braintree's priority-first syncs fetch the most recent 2 days' worth of data from the CREDIT_CARD_VERIFICATION table. To learn more, see our priority-first sync documentation.

January 2023

We have upgraded our Braintree connector from version 2.108.0 to 3.19.0 of the Braintree API. For more information about the changes and deprecations, see Braintree API's changelog.

October 2022

The Braintree connector now supports table blocking for all Braintree tables. You can now choose which tables to sync and which to block from syncing to your destination. On your Connector Details page, go to the Schema tab and select or deselect the tables. If you want to sync a child table, you must include the parent table in the sync.

May 2021

We have added a new table, DISPUTE_STATUS_HISTORY, which stores a dispute's status change history. For more information, see Braintree's documentation.

April 2021

We have improved the sync speed of the Braintree connector by implementing parallelism in our syncs.

September 2020

We have added a new table, LOCAL_PAYMENT_DETAILS. See Braintree's documentation for more information.

July 2020

We have added a new column, trial_duration, to replace the trail_duration column in the SUBSCRIPTION table. We will discontinue the replaced column after November 1, 2020. Be sure to update your queries with the new column name before we discontinue the old column.

June 2020

We have improved the sync speed for our Braintree connector by changing the sync strategy of the TRANSACTION table. We now use multiple API calls with filters to sync data from the TRANSACTION table.

May 2020

We have improved the sync speed for our Braintree connector. We have modified our connector settings to minimize READ_TIMEOUT exceptions from Braintree, which will help prevent timeout errors during our syncs.

We have added six new tables:

• PLAN
• TRANSACTION_LINE_ITEM
• SAMSUNG_CARD_DETAILS
• CREDIT_CARD_VERIFICATION
• PAYPAL_HERE_DETAILS
• US_BANK_ACCOUNT_DETAILS

We have added the following fields to the tables below:

• country_code_numeric to the CUSTOMER_ADDRESS table
• fax to the REGISTERED_CUSTOMER table
• network_tokenized to the ANDROID_PAY_DETAILS table
• expiration_date to the MASTERPASS_CARD_DETAILS table
• address_* and funding_details_* to the MERCHANT_ACCOUNT table
• customer_id, expiration_date, and address_* to the CREDIT_CARD table
• plan_id, description, next_billing_amount, and descriptor_* to the SUBSCRIPTION table
• plan_id, authorization_expires_at, escrow_status, gateway_rejection_reason, retrieval_reference_number, shipping_amount, shipping_from_postal_code, billing_adress_*, descriptor_*, network_response_*, processor_response_*, risk_data_*, shipping_address_*, and three_d_secure_info_* to the TRANSACTION table
• merchant_account_id, amount_won, case_number, created_date, currency_iso_code, dispute_amount, original_dispute_id, processor_comments, reason_code, reason_description, reference_number, and updated_date to the DISPUTE table
• plan_id to the TRANSACTION_DISCOUNT, SUBSCRIPTION_DISCOUNT, TRANSACTION_ADD_ON, and SUBSCRIPTION_ADD_ON tables

April 2020

We now support Braintree Java SDK version 2.108.0.

March 2020

We have added a new field, processor_authorization_code, to the TRANSACTION table.

January 2019

The transaction_id column is now the primary key in the TRANSACTION_ADD_ON table.

April 2018

We now re-sync all subscriptions once a day to ensure that we capture every change. Previously, we only synced new subscriptions.

Transactions with the status SETTLEMENT_DECLINED no longer cause repeated re-syncs.

Out-of-date SUBSCRIPTION_ADD_ON and SUBSCRIPTION_DISCOUNT rows are now properly deleted when you edit these subscriptions. Previously, it was possible to be left with extra rows when you reduced the number of add-ons or discount lines in a subscription record.

We have added support for logs for the following connectors:

• Braintree
• Apple App Store (formerly iTunes Connect)
• Kantata