Define: PG (Payment Gateway) Fee

What PG (Payment Gateway) Fee Means in a Contract

A PG (Payment Gateway) Fee is a defined cost item in a commercial contract that accounts for charges incurred through third-party payment processing infrastructure used to collect revenue from end users. This fee arises whenever a business relies on an external service provider, such as a card processor or digital wallet operator, to complete transactions on its behalf within a specified market or territory.

The term is most often found in revenue-sharing, licensing, or platform agreements where one party collects money from customers and must pass a share of that money to another party. Because the payment gateway itself takes a cut before funds are distributed, contracts need to clarify who bears that cost and how it is calculated, so that both parties understand the net amount that will actually be shared or reported.

This clause is a financial mechanic rather than a broad payment obligation. It does not describe how or when the parties pay each other; it describes a specific deduction tied to the infrastructure used to process customer payments, and it usually appears alongside broader royalty, commission, or revenue-share provisions.

How PG (Payment Gateway) Fee Is Defined or Measured

Most agreements define the PG (Payment Gateway) Fee as a percentage of gross transaction revenue collected through the gateway. This percentage is usually capped at a specified maximum, giving both parties predictability over how much of the revenue stream will be absorbed by processing costs before any further splits occur.

Measurement is typically tied to the actual amounts charged by the gateway provider, meaning the fee can fluctuate with market rates unless the contract fixes it at a flat rate. Some agreements distinguish between fees applicable in different territories, since payment gateway costs can vary significantly by country due to local banking rules, currency conversion, and card network charges.

• Percentage-based cap on gross transaction value
• Territory-specific rate schedules
• Requirement for written amendment if fees exceed the cap
• Obligation to notify the other party in writing of any rate change

Because the fee is often set by an outside processor rather than either contracting party, agreements frequently include a mechanism for updating the rate without renegotiating the entire contract, provided any increase above the agreed cap is formalized through a written amendment.

Where PG (Payment Gateway) Fee Appears in Agreements

This term commonly appears in cloud services agreements and other platform-based arrangements where a vendor collects payments from end users on behalf of, or in coordination with, another party. It is also relevant in broader payment agreements that govern how transaction-related deductions are handled before funds are remitted.

Industries that rely heavily on digital transactions, such as technology, gaming, and retail, tend to include detailed PG (Payment Gateway) Fee clauses because payment processing costs represent a meaningful portion of overall transaction value. In the gaming sector, for example, in-app purchases and microtransactions often route through third-party gateways, making this fee a material line item.

The clause is typically placed within the financial terms or revenue-sharing section of an agreement, often near definitions for gross revenue, net revenue, and applicable taxes, since the PG (Payment Gateway) Fee directly affects how those figures are calculated.

Why the Exact Wording Matters

Precision in this clause matters because even small percentage differences can have a significant cumulative effect on revenue split between the parties, especially in high-volume transaction environments. Vague language about which fees are included or excluded can lead to disputes over whether currency conversion charges, chargebacks, or refund-processing costs fall within the defined PG (Payment Gateway) Fee.

The requirement for a written amendment when fees exceed the cap is a critical control mechanism. Without it, a party could unilaterally pass through increased processing costs, eroding the other party's expected revenue share. Clear notice obligations also ensure that any change is documented and enforceable under the law governing the contract, rather than relying on informal communication.

Ambiguity about territory-specific rates can also cause confusion when a business expands into new markets, since payment gateway costs are rarely uniform across regions.

Drafting Considerations

Drafters should specify exactly what costs are included in the PG (Payment Gateway) Fee, such as processing charges, currency conversion, and chargeback fees, to avoid later disagreement. It is also wise to state clearly whether the cap applies per transaction, per period, or across an entire territory.

Including a defined process for rate changes, requiring written notice and, where the cap is exceeded, a formal amendment, helps prevent unilateral cost shifting. Parties drafting a supply of services agreement involving recurring end-user payments should consider referencing this fee structure directly within the payment terms to maintain consistency across related clauses.

Finally, parties should consider how the PG (Payment Gateway) Fee interacts with tax provisions and revenue reporting obligations, ensuring that gross and net revenue definitions align with how the fee is calculated and deducted.