Platforms & Channels
Compare subscription routes and seller channel readiness.
Digital CEO has an existing Base44 Android wrapper. It can check access for a signed-in account. Google Play Billing and iOS billing are unavailable in the current source. The web checkout and signed webhook require end-to-end acceptance. Seller channel connections require separate authorisation.
Digital CEO subscriptions
Website
Wix confirms the order and the webhook verifies the signed event before granting anything.
A renewal cannot extend the record: the webhook treats an already-paid purchase as terminal and returns early, and a subscription row has no paid-through date to extend.
The subscription-cancelled event revokes access.
The subscription-expired event revokes access.
No code exists for this. No refund event is registered, so a refunded subscription keeps access.
No code exists for this. There is no grace period — a failed payment arrives as a cancellation, which ends access at once.
Access lives on the account, not the device, so signing in anywhere restores it with nothing to restore.
Wix collects from the buyer and settles to Digital CEO’s own merchant account and bank account.
WIX_CHECKOUT_API_KEY and WIX_CHECKOUT_SITE_ID are already set.
App not published; there is no verified live purchase, renewal or refund run. These are code paths, not proven transactions.
Android app
Requires a server call to the Play Developer API with the purchase token, authenticated by a service account. The current wrapper cannot issue a Google Play purchase token.
Requires Real-time developer notifications (SUBSCRIPTION_RENEWED) delivered through Cloud Pub/Sub.
Requires SUBSCRIPTION_CANCELED, applied as auto-renew off with access running to the paid-through date.
Requires SUBSCRIPTION_EXPIRED.
Requires the voided-purchase notification, plus the pending-refund-review notification for chargebacks.
Requires SUBSCRIPTION_ON_HOLD and SUBSCRIPTION_IN_GRACE_PERIOD, and SUBSCRIPTION_RECOVERED when the payment later succeeds.
Requires re-querying current purchases on sign-in and honouring SUBSCRIPTION_RESTARTED.
Google collects from the buyer and pays Digital CEO to the payments profile on the Play developer account, after Google’s service fee.
None. A service account with Play Developer API access would be required.
The existing Base44 wrapper does not support Google Play Billing.
iPhone app
Requires the App Store Server API to verify the signed transaction, not a receipt parsed on the device.
Requires App Store Server Notifications V2 and the renewal event.
Requires the renewal-status change notification, applied as auto-renew off with access to the period end.
Requires the expiry and failed-renewal notifications.
Requires the refund notification, which must withdraw access.
Requires the billing-retry and grace-period notifications. Apple grants a grace period only if it is switched on for the product.
A restore mechanism is required by the App Review Guidelines before the app can ship at all.
Apple collects from the buyer and pays Digital CEO to the bank account on the Apple developer account, after Apple’s commission.
None. An App Store Server API key (key id, issuer id, .p8) would be required.
There is no iOS build in this project at all.
What Apple’s rules require of this design
One account, whichever platform paid
Every platform grants the same access, so access is checked across all of them at once. A user who already has access is never sold a second subscription — that is the rule that stops the same person being charged twice for signing in somewhere else.
Sign in to see this account’s own access decision.
These are local access-decision cases, not store billing or payment tests. What is missing is the other end: no Google Play or App Store purchase can reach this app yet, so a subscription can only actually arrive from the website.
Seller storefronts
Four separate integrations, each requiring its own seller authorisation and end-to-end proof. The Base44 Wix connector offers per-user authorisation, but no seller connection has been registered or tested.
Wix
Digital CEO registers as its own Wix app in the Wix developer centre, and Wix sets the API permissions on that app rather than at sign-in time — the only OAuth scope is offline_access.
The seller signs in with their own Wix account and approves Digital CEO on their own site. No API key is ever asked of the seller.
Products are created in the seller’s own Wix Stores catalogue, so the seller’s own pricing, tax and store policies apply.
Orders and payment status are read through the seller’s own connection, plus Wix app webhooks signed with the app’s public key.
On the seller’s own site: the digital product and its file live there, and access is the seller’s to grant.
Wix Payments charges the buyer and pays the seller’s own bank account. Digital CEO never receives, holds or splits it.
No store is connected for this channel.
To reach connected: Digital CEO’s own Wix app registration, its credentials, a published callback URL, the seller’s authorisation and one real end-to-end test order.
Shopify
Digital CEO registers its own Shopify app with client credentials, and app review is required before it can be installed on stores it does not own.
The seller enters their own shop handle, then approves Digital CEO on their own store. The handle only builds the authorise URL; the connection is bound to the shop Shopify returns.
Products are created in the seller’s own Shopify catalogue through the Admin API.
Admin API order access plus webhooks signed with the app client secret (HMAC-SHA256).
Fulfilment is recorded against the seller’s own order, and the digital file is delivered by the store’s own download mechanism.
Shopify Payments settles to the seller’s own bank account. Digital CEO never receives it.
No store is connected for this channel.
To reach connected: A Shopify app credential, app review, a published callback URL, a shop install and one real end-to-end test order on a development store.
eBay
An eBay developer account with a production keyset, a registered RuName pointing at this app’s callback, and eBay’s compliance checks completed.
The seller authorises Digital CEO on eBay’s own consent screen.
Listings are created in the seller’s own inventory through the eBay Inventory API. Digital downloads are restricted to sellers approved in eligible categories.
Order events arrive through the eBay Notification API, after the endpoint verification handshake.
Fulfilment is recorded against the seller’s own order.
eBay manages the payment and pays the seller directly. Digital CEO never receives it.
No store is connected for this channel.
To reach connected: eBay credentials, the callback and notification endpoints registered, eBay compliance, a seller authorisation and one real end-to-end test order.
Etsy
Digital CEO registers its own Etsy app (OAuth with PKCE) in the Etsy developer portal; Etsy reviews new apps before they can serve other sellers.
The seller authorises Digital CEO on Etsy’s own consent screen; their shop id is read back from Etsy, never taken from the browser.
Listings are created in the seller’s own shop through the Etsy Open API v3. Etsy delivers digital listings as uploaded files.
Etsy has no order webhooks: receipts are read by a scheduled pull with the seller’s own token.
The file is attached to the listing on Etsy, so the buyer receives it from Etsy.
Etsy takes the payment and pays the seller through their own Etsy Payments account. Digital CEO never receives it.
No store is connected for this channel.
To reach connected: Etsy app credentials and app review, a published callback URL, a seller authorisation, the scheduled pull and one real end-to-end test order.
Amazon
A Seller Central developer registration and an SP-API application approved by Amazon, with Login with Amazon credentials and the application id.
The seller authorises Digital CEO through Login with Amazon from their own Seller Central account.
Listings are submitted to the seller’s own catalogue through the SP-API. Digital software needs an approved seller and the right category.
Order change notifications arrive through Amazon SNS and are verified before being trusted.
Fulfilled by Amazon or by the seller, per that seller’s own setup.
Amazon pays the seller from their own disbursements. Digital CEO never receives it.
No store is connected for this channel.
To reach connected: The approved SP-API application, its credentials, a published callback URL, the notification subscription, a seller authorisation and one real end-to-end test order.