Enterprise agreements — how the subscription is billed

An enterprise agreement adds a monthly subscription alongside your transaction fees. It is billed as a MINIMUM, not an addition.

What that means on your invoice:
• Each month you pay your transaction fees or your subscription, whichever is greater. Never both.
• In a lower-volume month the subscription is what you pay, and your transaction fees count toward it.
• Once your volume grows to where the transaction fees alone exceed the subscription, the subscription stops appearing on your invoice entirely. You just pay the transaction rate.

Why it works this way:
The subscription exists to fund the parts of an enterprise relationship that have real cost and do not scale with your payment volume — a SOC 2 attestation somebody has to audit, contractual response times, a named person on the phone. At lower volume the transaction rate does not cover those. At higher volume it does, and charging the subscription on top would be charging you twice for the same thing.

What an agreement never does:
• It never prices you below the published bands. The minimum is a floor on the relationship, not a discount on the transaction rate.
• It never unlocks a feature. SSO, SCIM, the audit chain, and one-click export ship to every organization on the platform including the smallest. An agreement adds people and paperwork, not capabilities.

Seeing it:
Account -> Usage shows the current month's estimate, and says which of the two is carrying the month — either your volume covering the subscription, or the subscription acting as the minimum. The figure there is produced by the same calculation that bills you.

Existing agreements:
Agreements signed before this change continue to bill as they always have, where the subscription adds to transaction fees. Nothing re-prices automatically. If you would like to move to the minimum model, ask your contact.