---
title: "Pax8 Integration: Subscription Sync"
url: "https://help.psarev.io/en/article/pax8-integration-subscription-sync"
language: "en"
last_updated: "2026-11-18T16:25:39.674Z"
---

# Pax8 Integration: Subscription Sync

The subscription sync keeps your Rev.io billing in step with what your customers have in Pax8. It runs two ways at once. Changes arrive in real time through a Pax8 webhook, usually within seconds, and a nightly check reviews every subscription to catch anything the webhook missed. Subscriptions sync one way, from Pax8 to Rev.io. The integration never cancels or changes a subscription in Pax8.

The subscription sync is controlled by the settings on the *Pax8 Subscription Sync* page of the integration setup. See the [Pax8 Integration: Configuration](https://help.psarev.io/en/article/pax8-integration-configuration) article for more information.

For each active Pax8 subscription, the integration makes sure Rev.io has everything needed to bill it.

1.  **Customer.** Matched or created using the same rules as the customer sync and the **Customer Creation Policy** setting. See the [Pax8 Integration: Customer and Contact Sync](https://help.psarev.io/en/article/pax8-integration-customer-and-contact-sync) article for more information.
2.  **Product.** Matched by SKU, or created when **Auto-Create Products** is on. New products use the **Recurring - Subscription** product type.
3.  **Cost.** The Pax8 partner cost is written to the product and its vendor row on the product's **Purchasing** tab.
4.  **License asset.** Created on the customer when **Auto-Create Assets** is on. Each asset is tagged with the subscription's unique ID so it is never duplicated.
5.  **Recurring service and line.** A Pax8 recurring service is added to the customer under the **Managed Services** service type, with a service line for the product that has the right quantity, cost, rate, and status.

On later runs, the quantity, cost, and rate on existing lines are updated only when they change.

| **NOTE:** If the **Managed Services** service type or the **Recurring - Subscription** product type does not exist in Rev.io, the subscription is skipped until the type exists. See the [Pax8 Integration: Prerequisites](https://help.psarev.io/en/article/pax8-integration-prerequisites) article for more information. |
| --- |

The integration writes your cost but leaves your sell price alone unless **Copy Suggested Retail Price** is on. When it is on, the Pax8 suggested retail price is copied to the rate on products the integration creates.

Some Pax8 products are priced as one flat amount for the whole subscription, no matter how many seats. The **Flat-Rate Subscription Billing** setting controls how these bill. In both options, the line quantity is set to 1 so the rate holds the full amount.

| **Option** | **Definition** |
| --- | --- |
| **bill-automatically** | *Writes the Pax8 flat price as the rate each time the sync runs.* |
| **hold-for-review** | *Leaves the rate blank and notifies you to enter the total flat amount in Rev.io.* |

Usage (metered) subscriptions, which are billed after the fact based on use, are skipped so they don't create recurring lines. A subscription is treated as usage when Pax8 marks it as usage-eligible, or when it has a quantity of 1 and no partner cost.

The integration also protects against cancelled subscriptions that have been renewed. When a cancelled subscription has an active replacement, such as a renewed New Commerce (NCE) subscription, its service line is not disconnected. 

When a subscription is cancelled in Pax8, what happens in Rev.io depends on whether the subscription has a commitment term, such as an annual contract.

| **Label** | **Definition** |
| --- | --- |
| **Committed Cancel Policy** | *Applies to subscriptions with a commitment term. **keep-to-commitment-end** keeps billing through the end of the term. **keep-and-flag** keeps the service active and sends an alert so you can review it. **disconnect** disconnects the service right away.* |
| **Month-to-Month Cancel Policy** | *Applies to month-to-month subscriptions. **disconnect** disconnects the service right away. **keep-and-flag** keeps the service active and sends an alert so you can review it.* |

Disconnecting a service stops billing. For committed terms, you often want to keep billing to the end of the contract even after a cancellation, and **keep-and-flag** does that while making sure nothing slips through without notice.

Because the nightly check can disconnect services, it includes a safety limit called the circuit breaker. If more than the **Circuit Breaker Threshold** percentage of your Pax8 subscriptions disappear between runs, the sync stops and alerts you instead of disconnecting them. For example, with the default of 50, if you had 1,000 subscriptions yesterday and only 400 today, the sync stops so you can check for a Pax8 outage, a connection problem, or a real large change. If the change is real, run **Reset Instance State** and let the sync run again. See the [Pax8 Integration: Notifications and Maintenance](https://help.psarev.io/en/article/pax8-integration-notifications-and-maintenance) article for more information.

Incoming webhooks are checked against the **Webhook Shared Secret**, the same value entered in your Pax8 portal. A webhook that doesn't match is rejected. If the secret is set to **disabled**, the webhook is not registered and subscriptions are kept current by the nightly check only.

The **Proration Behavior** setting controls when a new service line starts billing. **No proration** starts the line at the next billing period, with no partial-month charge. **Prorate** starts the line today, so Rev.io bills a prorated amount for the rest of the current period.

For more information about the Pax8 integration, see the following articles.

[Pax8 Integration: Overview](https://help.psarev.io/en/article/pax8-integration-overview)  
[Pax8 Integration: Configuration](https://help.psarev.io/en/article/pax8-integration-configuration)  
[Pax8 Integration: Frequently Asked Questions](https://help.psarev.io/en/article/pax8-integration-frequently-asked-questions)
