How PayloadAPI Combines Monthly Plans with a Shared Usage Wallet

When API traffic changes, two questions matter:What will the extra usage cost, and when should requests stop?

A monthly plan can make your baseline easier to budget for. Pay-as-you-go can suit workloads whose demand is still uncertain. Neither choice removes the need to understand what happens during a busy week.

PayloadAPI brings these options into one workspace. Monthly subscriptions provide an included request allowance. A shared organization wallet funds pay-as-you-go usage and eligible overages. You decide whether a supported monthly plan can continue beyond its included quota.

Availability: Paid checkout is subject to PayPal marketplace approval. Check the marketplace for current availability.

Here is how the pieces fit together.

#Two payment paths, clearly defined

Monthly subscriptions and the organization wallet serve different purposes:

Topping up your wallet does not pay or renew your monthly subscription.Monthly fees are billed separately. Included calls have no additional per-request wallet charge.

The shared wallet gives your organization one pool of prepaid funds for usage across its APIs. For example, a pay-as-you-go API and a monthly API with overages enabled can both draw from that balance. Spending on either reduces the amount available to the other.

#A traffic spike, with the full cost shown

Consider this illustrative monthly plan:

• Subscription fee:$49 per month

• Included allowance:50,000 requests per billing period

• Overage rate:$0.005 per additional billable request

Assume the plan supports overages, you have enabled them, and your wallet balance and spending cap can cover the extra usage.

If your application makes 62,000 billable requests during the period, the calculation is:

The $49 subscription fee is billed separately, and $60 is consumed from the prepaid wallet. A top-up adds funds to that wallet; it is not an additional usage charge to count again in this calculation.

To serve all 12,000 extra requests, at least $60 must be available for those overages, after accounting for other wallet-funded usage. Any configured overage cap must also allow that amount. A $50 available balance would cover only 10,000 additional requests at this rate unless you add more funds.

Prices are illustrative and shown in USD before any applicable taxes. Check the selected plan's current terms and checkout details.

#Choose what happens when you reach the quota

At checkout, monthly plans that support overages offer an“Allow overage requests”option.

Leave it disabled and requests beyond the included allowance are refused. This avoids per-request overage charges for that subscription, although its recurring base fee still applies.

Enable it and eligible additional requests can use your prepaid balance at the displayed rate. You can also set aMonthly Overage Spending Capduring checkout to limit that subscription's additional usage spending.

For example, with the illustrative plan above, a $20 overage cap allows up to 4,000 additional billable requests at $0.005 each, provided sufficient wallet funds remain available.

Overages do not remove rate limits or guarantee uninterrupted service. Requests can still be refused when a spending cap is reached, funds are insufficient, or the plan's rate limit is exceeded. Your application should handle these responses appropriately.

#Get a warning before the allowance runs out

PayloadAPI supports quota notifications in the workspace and email alerts to the organization owner. The default thresholds are50% and 90%, and you can customize thresholds for your subscription.

For a 50,000-request allowance, those defaults correspond to 25,000 and 45,000 requests used. That gives you opportunities to review usage, check your balance, and decide whether to add funds before entering overage territory.

Notifications follow usage processing, and email delivery can introduce a delay. Configure your spending choices in advance so that request handling follows your settings even before you read an alert.

#How the gateway checks usage

PayloadAPI's gateway uses Cloudflare Durable Objects to coordinate quota and prepaid-usage reservations before forwarding requests. Signed route snapshots provide routing and entitlement information without querying the central application database for every API call.

Detailed usage events travel through Cloudflare Queues for background processing. This separates request admission from later usage reporting and accounting work.

Cached snapshots can support continued routing during some control-plane interruptions, subject to freshness limits and the availability of the gateway's other dependencies. Actual latency and availability depend on operating conditions.

#Choose a plan around your workload

Start with your expected demand. A monthly plan can suit an application with a consistent baseline when its included allowance and price fit your usage. Pay-as-you-go can suit a workload that is smaller, intermittent, or difficult to forecast.

A monthly plan still commits you to its base fee when you use fewer calls. Compare the expected total at your normal traffic level and during a spike, including any overages.

Before activating a plan, check its included allowance, unit rate, renewal terms, and rate limits. For monthly plans, decide whether to enable overages and what additional spending you are comfortable allowing. For all wallet-funded usage, remember that other APIs share the available balance.

Explore the [PayloadAPI marketplace](https://payloadapi.com/apis), compare the plans for your API, and review the billing breakdown when checkout is available.