Issue with Rate Plan Subscription Duration in Apigee OPDK 4.52 Monetization

Dear Team,

I would like to raise a concern regarding an issue encountered in Apigee OPDK 4.52.00 related to monetization and rate plan subscriptions.

We have configured a rate plan with the following details:

  • Effective Date: March 23, 2025

  • End Date: Not defined (open-ended)

One of the developers subscribed to this rate plan as a prepaid subscription with a duration of one year, starting from October 30, 2025 until October 30, 2026.

However, we observed unexpected behavior where the developer’s subscription ended prematurely on February 28, 2026 (approximately after 4 months), and the account balance became negative.

We would appreciate your support in clarifying the following:

  1. What could be the reason behind the subscription ending earlier than the configured one-year period?

  2. Is the rate plan’s effective date impacting the subscription duration or billing cycle in this scenario?

  3. How can we ensure that a developer’s subscription remains valid for the full purchased duration (e.g., one year), regardless of the rate plan’s effective date?

  4. Can the same developer resubscribe to the same rate plan after recharging their balance without needing to create a new rate plan?

For your reference, I will attach screenshots of the rate plan configuration and related details.

Please let me know if any additional information is required.

Best Regards,

Developer Balance

{

    "developerBalance": [

        {

            "amount": -4500000.0000,

            "chargePerUsage": false,

            "id": "da78c077-3482-47b6-80e4-847330a0cecd",

            "isRecurring": false,

            "supportedCurrency": {

                "description": "Saudi Arabia Riyals",

                "displayName": "Saudi Arabia Riyals",

                "id": "sar",

                "minimumTopupAmount": 100.0000,

                "name": "SAR",

                "organization": {

                    "approveTrusted": false,

                    "approveUntrusted": false,

                    "billingCycle": "CALENDAR_MONTH",

                    "country": "SA",

                    "currency": "SAR",

                    "description": "tcc",

                    "hasBillingAdjustment": true,

                    "hasBroker": false,

                    "hasSelfBilling": false,

                    "hasSeparateInvoiceForProduct": false,

                    "id": "tcc",

                    "issueNettingStmt": false,

                    "name": "ttt",

                    "nettingStmtPerCurrency": false,

                    "selfBillingAsExchOrg": true,

                    "selfBillingForAllDev": false,

                    "separateInvoiceForFees": false,

                    "status": "ACTIVE",

                    "supportedBillingType": "BOTH",

                    "taxEngineExternalId": "APIGEE01",

                    "taxModel": "HYBRID",

                    "timezone": "Asia/Riyadh"

                },

                "status": "ACTIVE",

                "virtualCurrency": false

            },

            "usage": 0

        }

    ],

    "totalRecords": 1

}

Hello @Amr, welcome back to the community! Thank you for the detailed breakdown of your question. While we wait for the community of experts to answer, you might find the following community resources helpful:

We look forward to seeing the community’s insights on this!

Hi
@dchiesa1 @dknezic @kurtkanaskie I need your kind support.

Hello @AlexET, please I need your support to reach this question to Google Team.

Hi Amr, welcome to the Apigee Community!

Based on your description, the early termination of the developer’s access is tied to the negative account balance rather than the date configurations. Here are the answers to your questions regarding how prepaid subscriptions work in this scenario:

1.Reason for early end: In Apigee, prepaid billing tracks a developer’s wallet balance in real time and will automatically block API calls if the developer has insufficient funds. Since the balance became negative, access was blocked despite the subscription timeline still being active.

2.Effective date impact: The rate plan’s effective date does not impact the subscription duration or billing cycle in a way that would cause this cutoff. The blockage is strictly enforced by the depleted prepaid wallet.

3.Ensuring validity: To ensure a prepaid subscription remains valid for the full purchased duration (e.g., one year), the developer must maintain a sufficient upfront balance in their wallet to cover their ongoing API consumption and any associated fees throughout that entire period.

4.Resubscribing/Recharging: Because the purchased subscription period (until October 30, 2026) is still technically active, the developer does not need a new rate plan. Recharging or topping up their wallet balance to a positive amount should restore their access.

Suggested Check: To understand why the balance was depleted in just four months, we recommend checking the API traffic and analytics for this developer. Were there any unexpected usage spikes or large dynamic consumption fees applied during that period?

Please let us know if you have any additional questions or if checking the usage logs reveals anything unusual.

Hi Amr, you can use Apigee analytics custom reports to verify the historical aggregate transactions. If you have never used it, you can also directly access to the Analytics and Monetization database, following the instructions on hour guide: https://docs.apigee.com/static/files/ApigeeEdgeTroubleshootingGuide.pdf