Overview

In Preczn, a Billing Group represents a fee group associated with a merchant at a specific connection. These groups determine the fees charged by the processor, such as transaction fees, monthly fees, or platform fees.

⚠️

Note: The actual fee definitions and logic are handled by the payment processor (PSP) — not within Preczn. Billing groups in Preczn are used to assign and move merchants between different predefined groups.

⸻

Supported Processors

Billing Groups are currently supported on the following connections:

⸻

Payrix

Preczn billing groups are paired to Payrix Groups. There are several methods for assigning and managing billing groups for merchants boarding to Payrix.

Option 1: Default Billing Groups (via Connection Drawer)

• Inside the connection drawer, you can configure default billing groups. This supports one or many billingGroups
• These will automatically be assigned to any merchant onboarded through this connection.

Option 2: Billing Group API Endpoints

• You can update billing groups after onboarding using the API.
• These updates synchronize changes with both Payrix and Preczn.
• You can read more about that in the section below

⸻

Rainforest

• By default, you do not need to specify the billingGroups for Rainforest. If not specified, the merchant will be assigned to the default billing group associated with your Rainforest platform.
• If you wish to override the deafult, you may set a billing group using the Preczn API only before boarding the merchant.
• Once boarded, Rainforest uses its default billing group, and no changes are allowed post-boarding. Any changes need to be handled with Rainforest directly

📎 Read more in Rainforest Docs

⸻

Billing Group API Endpoints

🛠️

These endpoints are currently only available for Payrix connections.

Overview:

• Each endpoint performs a remote operation to either pull or mutate data at the connection
• Each successful request syncs the latest billing groups associated with the merchant
  • This data can be found in the request body in the connections array. Look for the `connections

Get Current Billing Groups

Description: Pulls current billing group data from the connection and refreshes the Preczn record. This is a read-only sync operation — no changes are made at the processor.

• Method: GET
• Endpoint: /v1/merchants/{merchantId}/connections/Payrix/billing-groups
• Effect: Pull-only. Updates the local record in Preczn based on the data at the connection

⸻

Add Billing Group

Description: Adds a merchant to a billing group on Payrix. After success, Preczn will automatically refresh all billing group assignments for this merchant.

• Method: POST
• Endpoint: /v1//merchants/{merchantId}/connections/Payrix/billing-groups
• Effect: Adds billing group remotely and syncs local state.

⸻

Delete Billing Group

Description: Removes a merchant from a billing group on Payrix. After success, Preczn will automatically refresh the billing group list for the merchant.

• Method: POST
• Endpoint: /merchants/{merchantId}/connections/Payrix/billing-groups/{payrixGroupId}
• Effect: Removes billing group remotely and syncs local state.

⸻

Additional Notes

• 🔁 Sync Behavior: After an add/delete operation, all billing groups for the merchant are re-synced from Payrix. • 🛑 Rainforest Restriction: Modifications must happen before onboarding. No post-boarding changes are supported. • 🔍 Logging: All billing group operations are tracked in Preczn for auditing.