CarbCheckBuddy Premium Checkout

Choose your plan, then continue through the secure purchase channel.

Monthly and Yearly unlock the same complete Premium feature set. Paid checkout remains in pre-launch mode until the coordinated release. When purchasing is enabled, review the selected price, amount due and renewal terms before confirmation.

✓ Monthly A$9.99✓ Yearly A$89.99✓ Secure recurring subscription
Selected plan
$—AUD / month

A$9.99 AUD per month for the full Premium feature set.

✓ Full Premium access✓ Monthly or Yearly membership✓ Account-based entitlement after validation
Purchase channel

Where do you want to subscribe?

Choose the route that matches the device or billing method you plan to use.

iPhone / iPad

Open CarbCheckBuddy from its App Store listing and complete the subscription through the app’s supported Apple purchase flow.

App Store subscription coming soon
▶

Android

Open CarbCheckBuddy from Google Play and complete the subscription through the supported Android billing flow configured for the release.

Google Play subscription coming soon
◎

Website checkout

Web checkout is prepared but intentionally held until coordinated launch. The configured billing links are preserved and can be enabled without rebuilding this page.

Website checkout opens at launchThe static website itself does not collect or store payment-card details.
Entitlement flow

Purchase is only step one.

Premium should be turned on after the purchase is verified, not merely because a checkout page was opened.

1Account identifiedUser signs in or is associated with a CarbCheckBuddy account.
2Purchase completedApple, Google or approved web checkout completes payment.
3Server validatesTransaction/subscription status is verified server-side.
4Premium enabledValidated entitlement is linked to the CarbCheckBuddy account.
Already subscribed?

Restore or manage access.

Use the app’s Restore Purchases option for eligible store purchases, or open your billing provider’s management portal for an eligible direct web subscription.

Launch safeguard

Do not place private Stripe keys, App Store credentials, Play credentials or webhook secrets in site-config.js. Live payment verification belongs on a secure backend.