BeWild ChatGPT Plus 3-Month Plan Renewal Fails Again in Month 3: Fixed by Canceling the Plan, With Observations on PHP Pricing and Codex Benefits

On October 29, 2026, the three-month ChatGPT Plus plan I purchased through BeWild finally completed its third-month renewal repair.

However, this was still not a successful automatic renewal.

Just like last month, I encountered the monthly payment failure issue again. Moreover, the repair process added an extra step this time: I had to go to the official ChatGPT settings to cancel the original Plus plan before returning to BeWild to submit the repair request.

This is something I find a bit puzzling.

I had already prepaid for three months of service, so why do I still need to monitor and handle the renewal myself every month?

To make matters more complicated, I had Codex tasks running at the time. I was worried that canceling Plus might affect the ongoing tasks, so I specifically contacted customer support.

Fortunately, the repair was ultimately successful.

In addition, there were two notable findings worth recording this time.

First, OpenAI’s new bill once again used PHP 982.14, which is Philippine Pesos. I am increasingly inclined to believe that BeWild’s choice of this regional pricing method may be related to reducing procurement costs and increasing profit margins.

Second, after canceling and resubscribing to Plus, Codex’s five-hour and weekly quotas initially retained their original remaining balances, but then both simultaneously restored to 100%, and even the next reset times changed. This makes me suspect that resubscribing may have triggered a quota reallocation, it just didn’t display immediately.

This article continues to document this actual experience and discusses my understanding of these phenomena.

1. The Same Three-Month Order: Renewal Failures in Both the Second and Third Months

Let’s first review the background of this order.

On August 26, 2026, I purchased a three-month ChatGPT Plus plan through BeWild.

The order amount was US$62.99.

This was a newly repurchased order.

Because an earlier three-month plan encountered a payment method failure in its final month, BeWild ultimately refunded the unfulfilled service, prompting me to repurchase.

The first month of the new order went quite smoothly.

On August 26, OpenAI successfully generated a paid bill for US$20.00, and ChatGPT Plus was activated normally.

But problems arose in the second month.

The automatic renewal on September 26 failed, and it wasn’t until September 28 that I restored the service using BeWild’s “Repair Subscription” feature.

At that time, the new OpenAI bill used PHP 982.14, and the next expiration date was updated to October 28.

For the full experience, you can refer to the previous article:

BeWild ChatGPT Plus 3-Month Order Month 2 Renewal Failure Tested: Subscription Repair Successful, Plus Benefits Sync Delayed

In the previous article, I specifically raised a question:

Would the third month renew automatically and normally on October 28?

Now, the answer is in.

The third month’s renewal failed again.

2. Expiration on October 28: Both BeWild and OpenAI Show Abnormalities

On October 29, I first went to the “My Orders” page on BeWild.

The three-month order originally purchased on August 26 was still there, and the amount remained US$62.99.

The “Repair Subscription” button was also visible on the right side of the order.

I then opened “My Subscriptions”.

It clearly showed that ChatGPT Plus:

Was overdue.

The expiration date was:

October 28, 2026.

Next, I went to the official ChatGPT billing page.

The English interface path is:

Settings → Billing

In the Transaction history, you can see the latest bill:

• October 28, 2026
• ChatGPT Plus
• PHP 982.14
• Due

Meanwhile, the previous bill from September 28 was marked as Paid.

So this was not just a one-sided display error on the BeWild page.

OpenAI officially also clearly recorded that the new payment cycle was not completed.

However, I also noticed a rather interesting situation.

Although the October 28 renewal had failed, my ChatGPT and Codex were still functioning normally on October 29.

This makes me suspect that bill expiration and the actual termination of access rights might not be completely synchronized.

I will discuss this issue in more detail later.

3. This “Subscription Repair” Required Canceling the Original Plus Plan First

Since I had successfully repaired it once last month, I originally planned to just repeat the same operation.

Navigating to:

BeWild → My Orders → Repair Subscription

But the prompt that popped up this time was different.

The system required me to:

First, go to ChatGPT, cancel the overdue plan in the official settings, confirm the cancellation takes effect, obtain a new Session, and then return to BeWild to submit the repair.

I initially didn’t understand why canceling was necessary.

After all, from a user’s perspective, I had already prepaid for three months of service.

If BeWild’s payment method for the renewal failed, the service provider should theoretically handle the payment issue, rather than asking the user to cancel the original plan themselves.

Of course, speculating from a technical perspective, this process might be intended to clear OpenAI’s original unpaid subscription state, making it easier to re-establish the payment relationship.

But this is just my speculation; customer support did not explicitly explain the backend technical mechanism.

What I care more about is the hassle caused by the actual operation.

Especially this time, I also had Codex tasks running.

4. Contacting Support: I Worried Canceling Plus Would Interrupt Codex Tasks

I raised the question with BeWild customer support.

Why did I have to cancel the official ChatGPT plan before repairing the subscription?

Could this step be automated by the system?

Customer support’s operational suggestion was to go to the ChatGPT billing page, find the cancel subscription entry, cancel the original subscription first, wait for the account to revert to the free state, and then return to BeWild to submit the repair.

But I had another practical question:

If I cancel ChatGPT Plus now, will the ongoing Codex tasks be interrupted?

Because I have been constantly using Codex lately to handle engineering tasks for the Go Learning & Documentation Translations project.

These tasks sometimes take a long time to execute.

I didn’t want the running development tasks to be forced to stop because of a subscription repair.

Customer support suggested I:

Finish executing them first, then click repair.

I felt this was more prudent.

Therefore, I decided to continue using Codex at the time, waiting until the current work was finished or this quota cycle was nearly exhausted before handling the Plus subscription.

This also exposed a new user experience issue:

Renewal failures from third-party top-up services have started to affect my development work schedule.

If it were just occasionally clicking “Repair Subscription”, it would be acceptable.

But now I also had to consider when to cancel the plan, whether it would affect Codex, and when access rights would be restored after the repair, which is clearly much more complicated.

5. How to Cancel the Plus Plan in the ChatGPT English Interface

Once I was ready, I re-entered the official ChatGPT Billing page.

At the bottom of the page, I found:

Cancel plan

Which means canceling the plan.

After clicking it, ChatGPT first popped up a window recommending switching to ChatGPT Go.

I didn’t intend to change plans, so I selected:

No thanks

and continued canceling Plus.

I then entered the final confirmation page.

The window title was:

Subscription Cancellation

It contained a rather important explanation.

The meaning was:

If you cancel the subscription, the paid Plus usage time will be retained; if the current cycle has not been paid, Plus benefits may end immediately.

This matched my situation at the time.

The October 28 bill was unpaid, and the previous cycle had already expired on October 28.

So I clicked:

Cancel subscription

The page then prompted:

Your subscription has been canceled

Meaning the subscription was successfully canceled.

It should be noted that I did not pay an extra monthly fee to OpenAI for testing purposes this time.

Because the three-month plan had already been paid to BeWild.

If I paid OpenAI through my own payment method at this point, it might have resulted in a duplicate purchase.

6. Returning to BeWild: The Original Order Repair Completed

After canceling the original official subscription, I returned to BeWild.

I obtained a new Session and submitted it according to the instructions on the “Repair Subscription” page.

The Session used here is part of the third-party top-up process provided by BeWild. A Session may contain valid login credentials, posing an account security risk. Therefore, this article only documents the operational process, does not display the Session content, and does not present it as a general security recommendation.

After submission, the original order status changed to:

Processing.

The page indicated that the backend repair task was being processed and I should check back later for the latest status.

Afterwards, I refreshed “My Subscriptions” again.

The ChatGPT Plus that previously showed “Overdue” now displayed as:

Active.

The expiration date was also updated to:

November 29, 2026.

At least from the BeWild subscription page, the third month had been successfully repaired.

There was also one aspect I was quite satisfied with this time.

The repair was still completed using the original three-month order, and I was not asked to purchase a new plan.

Compared to the previous process of refunding and repurchasing, this was indeed simpler.

It’s just that the operation of canceling the official subscription first added an extra step.

7. OpenAI Bill Also Successfully Restored, Old Bill Voided

To confirm the repair result, I continued checking the official ChatGPT bills.

This time, I finally saw a change.

The original PHP 982.14 due bill from October 28:

Due → Void

Meaning it changed from due to voided.

At the same time, a new entry appeared on October 29:

• ChatGPT Plus
• PHP 982.14
• Paid

Now, let’s organize the OpenAI bills for this three-month order:

Date	Amount	Final Status
2026-08-26	US$20.00	Paid
2026-09-26	US$20.00	Void
2026-09-28	PHP 982.14	Paid
2026-10-28	PHP 982.14	Void
2026-10-29	PHP 982.14	Paid

These bills indicate:

The first cycle was paid normally on August 26.

The second cycle’s payment failed on September 26 and was successfully repaired on September 28.

The third cycle’s payment failed on October 28 and was successfully repaired on October 29.

Therefore, looking at the actual payment results, the monthly subscription fees for all three months were ultimately processed.

However, neither of the two subsequent months renewed automatically and successfully.

Additionally, the top of the latest billing page still retained a warning about potential payment issues. Therefore, I primarily confirmed the repair result based on the new Paid bill, the old Voided bill, and BeWild’s “Active” status, rather than assuming all system interfaces had immediately completed synchronization.

8. Why Use Philippine Pesos Continuously? I Lean Towards Cost and Profit Considerations

There was also a question that interested me this time.

Why does BeWild repeatedly use PHP 982.14 to pay for ChatGPT Plus?

Here, PHP stands for Philippine Peso.

According to OpenAI’s official multi-currency billing explanation, ChatGPT subscriptions support various local currencies, including the Philippine Peso, and different regions may adopt localized pricing.

Official documentation:

OpenAI: Multi-currency billing

I also checked the price of ChatGPT Plus in different regions.

As of October 29, 2026, the third-party price database AISub provided the following reference price for ChatGPT Plus on the web in the Philippines:

PHP 982.14/month

Which converts to approximately:

US$15.34/month

Meanwhile, the standard price in the United States is:

US$20/month.

This means that, based on the exchange rate and pricing method used by that database at the time, the price in the Philippines was about 23% lower.

Reference source:

AISub: Regional Price of ChatGPT Plus in the Philippines

This website also listed the Philippines as the region with the lowest web reference price for ChatGPT Plus among its tracked regions.

Of course, this is just the statistical result of a third-party database and should not be directly interpreted as OpenAI officially designating the Philippines as the globally lowest price forever.

Price rankings may change with exchange rates, local taxes, and pricing adjustments.

But at least one thing is quite clear:

The Philippine regional reference price corresponding to PHP 982.14 is indeed lower than the standard US$20 monthly fee in the United States.

Lower-Priced Regions May Provide Profit Margins for Top-Up Platforms

This is the explanation I am now more inclined to believe.

For third-party top-up platforms, if they can use legally available regional prices to purchase the same ChatGPT Plus service at a lower cost, then the price difference could become part of their business model.

Assume a month of Plus is purchased at the Philippine price of about US$15.34 at the time.

And the actual average monthly fee paid by the user through the top-up platform is about US$21.

There is a price difference between the two.

Of course, this is just the difference between revenue and the base procurement price, not the final profit.

The platform also has to bear payment processing fees, exchange rate costs, after-sales service, failed refund costs, and payment channel maintenance expenses.

But as long as overall costs are well controlled, regional price differences could potentially bring higher profit margins.

This is easier to understand than simply asking “why doesn’t the platform use US$20 instead of PHP 982.14”.

I am increasingly inclined to believe:

Choosing a lower-priced regional pricing method is likely a means for third-party top-up platforms to control costs and increase profit margins.

However, I must still distinguish between facts and speculation here.

The fact is, I have seen PHP 982.14 multiple times in OpenAI bills.

It is also a fact that the corresponding regional reference price for the Philippines is significantly lower than that of the United States.

But whether BeWild specifically chose the Philippines to expand profit margins, what payment channels they actually use, and how much transaction cost they bear are things I have no backend data to confirm.

Therefore, for now, this can only be viewed as a commercially plausible explanation, not a confirmed internal operational mechanism.

Based on My Order, How Much Price Difference Might the Platform Have?

My three-month plan actually cost:

US$62.99

Averaging about:

US$21.00 per month

If we assume all three months were procured at the US$15.34 reference price:

3 × US$15.34 = US$46.02

Compared to the US$62.99 I paid, the difference is:

US$16.97

But my actual bills did not use Philippine Pesos for all three months.

The first cycle was US$20.00.

The latter two cycles used PHP 982.14.

If we do a rough estimate based solely on the public reference exchange rate:

US$20.00 + US$15.34 + US$15.34 = US$50.68

Compared to US$62.99, the theoretical difference is about:

US$12.31

This calculation can only serve as a business model analysis and should not be considered the actual profit BeWild made from my order.

Because there are no actual exchange settlement records, nor data on processing fees, taxes, and after-sales costs.

Additionally, this reminded me of one thing.

The fact that a top-up platform uses a lower regional price does not necessarily mean consumers will enjoy the same proportional discount.

The actual three-month fee I paid was US$62.99.

Calculated at OpenAI’s standard US price of US$20/month, three months would only cost US$60, excluding potentially applicable taxes.

So my choice to use a third-party top-up service was primarily to solve actual payment channel issues, not because this three-month plan was cheaper than the official US standard price.

9. After Canceling and Resubscribing to Plus, Why Did Codex Quotas Subsequently Restore to 100%?

This repair also gave me new insights into Codex’s subscription status.

On October 28, ChatGPT Plus theoretically entered a new billing cycle.

But the automatic payment failed that day.

By October 29, I was still able to use ChatGPT Plus and Codex normally.

And recalling last month’s experience, my impression was that after the renewal anomaly occurred, the account still showed Plus for a period of time and didn’t immediately revert to Free.

This indicates that, at least in my actual experience:

Bill payment failure, abnormal plan status display, and the actual termination of usage rights do not necessarily occur at the same time.

As for the reason, I have a few guesses now.

One possibility is that after a payment failure, the system still retains a brief service grace period.

Another possibility is that there is a synchronization delay between the billing system, the ChatGPT frontend, and Codex’s permission status.

Yet another possibility is that currently established Codex sessions can still use the existing authorization state for a period of time.

However, none of these mechanisms were individually verified through this operation.

I can only confirm the phenomena I actually observed and cannot assert which specific cause it is.

After Resubscribing, Codex Quotas Initially Did Not Change

On October 29, after the third month’s subscription repair was successful, I entered Codex again and ran /status to check the quotas.

I was using Codex v0.164.0, the model was GPT-6.1-Sol (reasoning high), and the account status showed Plus.

However, the five-hour quota and the weekly quota did not immediately return to 100% just because of the new payment:

• Five-hour quota: 23% remaining, next reset time at 19:43 on October 29;
• Weekly quota: 44% remaining, next reset time at 15:29 on November 4.

From this screenshot, after the successful resubscription, Codex quotas did not reset immediately. I concluded at the time that Codex’s usage quotas might carry over the original cycle and would not be directly recalculated with the monthly Plus subscription payment.

But a second check about half an hour later changed this judgment.

Subsequently, Both Quota Windows Simultaneously Restored to 100%

Still on October 29, I ran the same /status command again. The Codex account still showed Plus, but the quotas had noticeably changed:

• Five-hour quota: changed from 23% remaining to 100% remaining;
• Weekly quota: changed from 44% remaining to 100% remaining.

Not only that, but the next reset times displayed for both quota windows also changed.

Item	First Check	Second Check
Account Status	Plus	Plus
Five-hour quota	23% remaining	100% remaining
Five-hour reset time	October 29, 19:43	October 29, 23:57
Weekly quota	44% remaining	100% remaining
Weekly reset time	November 4, 15:29	November 5, 18:57

This is a phenomenon I find particularly worth recording during this repair process. If you only look at the first screenshot, you would conclude that “resubscribing did not reset the quotas”; but combined with the second screenshot, the actual situation is “they did not reset immediately, but subsequently both quota windows simultaneously restored to 100%”.

The Two New Reset Times Seem to Point to the Same Starting Point

In the second screenshot, the five-hour quota shows a reset at 23:57 on October 29, while the weekly quota shows a reset at 18:57 on November 5.

If we reverse-calculate based on five hours and seven days respectively, both times point to around 18:57 on October 29.

In other words, this is unlikely to be a standalone natural reset of the five-hour window, because the weekly quota also went from 44% to 100%, and the next reset times for both windows changed together.

An explanation more consistent with the screenshot phenomena is that Codex re-established two quota cycles around this time, or the system synchronized a quota adjustment to the current session. The 18:57 here is reverse-calculated from the reset time and is not an operation time confirmed by backend logs.

Likely Related to Resubscribing, but Causality Cannot Yet Be Proven

Considering that I had just canceled the original Plus subscription that day, and then repaired and re-established the monthly subscription through BeWild, after which the Codex quotas simultaneously restored to 100%, I am now more inclined to believe that this quota change is related to resubscribing.

One possibility is that the new subscription was successfully paid, but Codex’s quota benefits require some time to be reallocated or refreshed, so the first check still showed the old quotas, and the second check showed the new 100%.

However, it is also impossible to rule out that OpenAI made a quota adjustment for a specific account, or that the quota display itself experienced a delayed update. Based solely on two /status screenshots, it is impossible to confirm the backend event that triggered the reset, and it cannot be asserted that this is an official unified reset.

Therefore, this experience can, at most, only show that: On my account, shortly after resubscribing to Plus, Codex’s five-hour and weekly quotas did indeed simultaneously restore to 100%, and the new reset times consistently point to around the same time. It cannot yet serve as an operational method guaranteeing that “canceling and resubscribing will reset quotas every time”.

For information on Codex quotas and usage limits, refer to the official OpenAI explanation: Using Codex with your ChatGPT plan.

So, Does Canceling Plus Interrupt Ongoing Codex Tasks?

There is another question that was not directly verified this time: during the period after the subscription was successfully canceled but before the repair was completed, would the ongoing Codex tasks definitely continue to run?

I discovered on October 29 that even though the previous day’s Plus payment failed, the account could still continue to use ChatGPT and Codex. This might involve a payment grace period, a synchronization delay for benefits across different systems, or the authorization state of an existing session, but the specific cause cannot be determined yet.

And these two quota screenshots were both obtained after this repair was completed. They only reflect Codex’s status after the repair and cannot prove that tasks running during the subscription cancellation period were definitely unaffected.

Therefore, if I need to handle similar issues in the future, I will still prioritize completing important Codex tasks before executing the cancel subscription and repair process. However, this observation made me realize that OpenAI’s billing status, Plus benefits status, and Codex quota windows may have different update rhythms.

10. After the Three-Month Order is Completed, My Evaluation of BeWild

Now, this three-month order purchased on August 26 has completed three payment cycles.

Looking at the results:

The first month was activated normally.

The second month’s renewal failed but was successfully restored after a repair.

The third month’s renewal failed again but was successfully restored after canceling the plan and repairing it again.

Therefore, I do not consider this a completely failed order.

After all, the subscription services corresponding to all three months ultimately completed payment processing.

Moreover, neither of the two subsequent repairs required me to purchase a new three-month plan.

At the same time, however, I cannot ignore its reliability issues.

Because the automatic renewals for the two subsequent months of this order both experienced abnormalities.

In other words, after purchasing the three-month plan, I actually still needed to proactively monitor every month:

• Whether it has expired;
• Whether the automatic payment was successful;
• Whether BeWild shows it as overdue;
• Whether the OpenAI bill is Paid or Due;
• Whether a repair is needed;
• Whether the benefits have fully synchronized after the repair.

Such a user experience still falls significantly short of my ideal three-month automatic renewal service.

Especially this time, I had to cancel the official ChatGPT subscription first before I could reapply for a repair.

For users who rely on Codex for development, they also need to specifically consider the timing of these operations.

This is not just a matter of clicking a few extra buttons; it has actually increased the cost of managing my work schedule.

As for the PHP 982.14 regional pricing, I actually think it is a quite understandable business choice.

If utilizing local subscription prices from different regions can reduce service procurement costs, then third-party platforms naturally have an incentive to choose lower-cost payment methods.

But regardless of how the platform controls procurement costs, as a user who has already prepaid, what I want most is still a stable subscription service.

Low-cost procurement may increase the platform’s profit margins, but it should not come at the cost of users frequently having to manually repair subscriptions.

11. Summary

This experience has yielded clear results.

On October 29, 2026, I completed the third month’s ChatGPT Plus renewal repair through BeWild.

The original PHP 982.14 due bill from October 28 became Void.

A new PHP 982.14 Paid bill was generated on October 29.

BeWild shows that Plus has been restored to active, with the expiration date updated to November 29.

Codex’s /status showed sequential but different results: the first check after the repair still showed 23% remaining for the five-hour quota and 44% remaining for the weekly quota; a later check showed both quotas simultaneously restored to 100%, and the next reset times changed accordingly.

For me, this hands-on test left three conclusions worth recording.

First, BeWild’s “Repair Subscription” feature can indeed resolve some renewal failures, but the fact that this three-month order failed to automatically renew for two consecutive months indicates that there is still room for improvement in service stability.

Second, Philippine Peso pricing has a clear regional price advantage. I believe third-party top-up platforms might choose this pricing method based on cost and profit considerations, but the specific profit structure still requires more evidence.

Third, OpenAI’s subscription bills, Plus benefits, and Codex quotas do not necessarily change synchronously. After resubscribing this time, Codex’s two quota windows initially did not change, but then simultaneously restored to 100%. I suspect this is related to a quota reallocation after resubscribing, but other system adjustments or synchronization delays cannot be ruled out.

These findings cannot indicate that all accounts and all subscription cycles will experience the same phenomena, but they can at least provide a practical reference for encountering similar situations in the future.

Currently, the third cycle’s payment for this three-month order has been completed.

I hope that in the future, I won’t need to maintain a prepaid service by canceling subscriptions, obtaining new Sessions, and manually applying for repairs. Otherwise, I might try to find other subscription options!

系列导航