What are the known limitations of the BlueSnap integration? – Help Center

The BlueSnap API is very limited in what it returns on an invoice line item. Thus, if you use the pricing plan type of "Initial Charge followed by Subscription" the MRR will reflect the inital charge in the first billing period, and then correct to the ongoing MRR beginning on the second period. The way to avoid this is to instead use two contracts in BlueSnap, one for the upfront one-time item and a second for the subscription.
Data can be delayed by up to one hour due to BlueSnap's reporting limitations.
Initial import of BlueSnap data can take a very long time due to rate limit and query performance by the BlueSnap API.
If you are using BlueSnap as a payment gateway only (Merchant-Managed Subscriptions or `On Demand`), SaaSync does not have access to the necessary information needed (invoices, subscriptions, etc) to properly operate.
When sending BlueSnap data to ChartMogul, we strongly recommend setting your churn recognition setting in ChartMogul to When the subscription ends in your billing system (default). This allows us to properly set the churn date that the billing system provides. This is a global setting and will affect all data sources.