Skip to content

Subscriptions FAQ

Do users who bought before we used EdgeKit get access?

Section titled “Do users who bought before we used EdgeKit get access?”

No. A grant is written by a purchase through EdgeKit checkout, and EdgeKit does not create grants from your billing provider’s existing records. A user subscription that never went through checkout appears on the Billing provider screens and gives no access.

Which billing providers can checkout charge?

Section titled “Which billing providers can checkout charge?”

Recurly only. EdgeKit reads both Recurly and Stripe records into the Billing provider screens, but checkout charges through Recurly. With Stripe as your active billing provider, checkout answers 409 billing_provider_unsupported.

Why does every checkout answer 409 no_billing_provider?

Section titled “Why does every checkout answer 409 no_billing_provider?”

Your organization has no active billing provider, or EdgeKit holds no Recurly API key for it. Both answer the same code and the message This site is not selling right now.. EdgeKit connects your billing provider; the console has no screen for it.

No. Recurly.js on your page turns the card into a token, and checkout accepts only that token. Its body is an allowlist of six keys. Any other key, number or cvv included, is refused with 400, and the message names the key, never its value.

No. An offer has at most one introductory discount, and every buyer of that offer gets it. What takes it off the charge is the billing provider coupon the offer names. See Add an introductory discount.

By default, no: a user gets one trial per product. Buying an offer marked The offer is the trial for a product the user already had a trial of answers 409 trial_already_used. The rule compares users, and users are told apart by email address, so ada+news@example.com is a different user from ada@example.com.

By default, access continues while your billing provider retries. If your billing provider gives up and ends the user subscription before the grant’s expiry, the grant is revoked with the reason dunning. If your organization’s Access during dunning is suspend, an unpaid invoice suspends the grant until it is paid. See How access follows your billing provider.

Nothing changes until the end of the paid period. A cancelled user subscription does not renew, so the grant is not extended and stops giving access at its expiry. Only a user subscription that ends before the grant’s expiry, or while the grant is suspended, revokes the grant.

Not on its own. When the user subscription also ends before the grant’s expiry, the grant is revoked with the reason refund or chargeback.

How do users cancel or change their payment details?

Section titled “How do users cancel or change their payment details?”

In your billing provider. EdgeKit hosts no account page and has no cancel request. Your page can list what a signed-in user holds with the browser client’s grants(), including expired, suspended and revoked grants.

Can EdgeKit cancel or refund in my billing provider?

Section titled “Can EdgeKit cancel or refund in my billing provider?”

No. Nothing in EdgeKit writes to your billing provider except the charge checkout makes. A grant change never cancels, refunds or pauses anything there.

Clear Purchasable or archive the offer, and deploy. Nothing already sold is revoked. To stop money moving at once, without waiting for a deploy, stop it in your billing provider.

No. Archiving a product revokes no grant, and checkout does not read a product’s status, so its offers keep selling until you stop each one.

Can I delete a product, an offer or a capability?

Section titled “Can I delete a product, an offer or a capability?”

No. The console has no delete action for any of them. Archive products and offers instead.

Why does checkout answer 409 offer_not_priced?

Section titled “Why does checkout answer 409 offer_not_priced?”

The offer has no active price for your active billing provider. EdgeKit maps your billing provider’s prices to your offers, and the offer’s Prices section shows the mapping. The console cannot change it.

No. Checkout charges the offer’s first active price for your billing provider, whatever the buyer’s location.

Can someone buy access for another person?

Section titled “Can someone buy access for another person?”

Yes. The grant goes to the user whose email address the buyer typed, and EdgeKit does not ask the buyer to prove the address. If no user has it, checkout creates one with the address not verified.

A signed-in user bought with a different email address. Who has the grant?

Section titled “A signed-in user bought with a different email address. Who has the grant?”

The user with the address typed at checkout. Checkout never reads the EdgeKit session.

Yes, when no user has the buyer’s address. Browsing anonymously never creates a user; buying does, before the card is charged, so the grant always has a user.

No. Requests with the same offer token converge on one purchase attempt, and a settled purchase answers its first result again, for up to an hour.

The card’s outcome is not known yet, and EdgeKit is resolving it in the background. Show the buyer that the purchase is still processing. Never show it as a failure, and never ask them to buy again.

12 hours by default. The lifetime applies to your whole organization, and EdgeKit sets it. A token can be sent again until it expires, so a declined card can be retried with it.

Does changing an offer’s product move people who already bought it?

Section titled “Does changing an offer’s product move people who already bought it?”

No. Purchases after the next deploy get a grant for the new product. Grants already written keep their product.

Does a product’s rank change what a user can read?

Section titled “Does a product’s rank change what a user can read?”

No. Rank picks which of a user’s grants is their membership, read as user.membership_level. Access is the union of all their grants.

Yes. Every active, unexpired grant they hold gives access. Buying a second offer is a second purchase and a second grant; checkout never changes an existing user subscription.

The model supports it: a grant held by a user organization reaches every member, and EdgeKit enforces a seat quota on it. Today, though, nothing in the console or the API writes a grant to a user organization, because checkout grants only the buyer. See User organizations.

Can a user buy access as a gift for someone else?

Section titled “Can a user buy access as a gift for someone else?”

Only by typing the other person’s email address at checkout: the grant goes to whoever holds that address. EdgeKit has no separate gift purchase. To share one piece of content, use a gift link. See Gift links.

Can I edit billing records in the console?

Section titled “Can I edit billing records in the console?”

No. The Billing provider screens are read-only. Change prices, accounts and user subscriptions in your billing provider.

Why are the Billing provider screens empty?

Section titled “Why are the Billing provider screens empty?”

Your billing provider has no such records, or EdgeKit has not synced them yet. EdgeKit runs the sync; the console has no sync control.

Can I change the access policy, trial reuse or seat overage?

Section titled “Can I change the access policy, trial reuse or seat overage?”

Not from the console. They are shown read-only under Configuration on each site’s screen in Delivery › Delivery › Sites, and EdgeKit sets them.

How quickly does a change in my billing provider reach a user?

Section titled “How quickly does a change in my billing provider reach a user?”

The grant moves when EdgeKit syncs the record, after your billing provider’s notification. In the browser, a user’s decisions read a signed copy of their grants that can be up to an hour old.

Is my billing data shared with other organizations?

Section titled “Is my billing data shared with other organizations?”

No. Your catalog, grants and the copy of your billing records live in your organization’s own database, which no other organization shares.