-
Notifications
You must be signed in to change notification settings - Fork 34
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
feat: offline billing accounts in org #638
Merged
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Member
kushsharma
commented
Jun 5, 2024
•
edited
Loading
edited
- Offline billing accounts are not registered in billing provider like Stripe by default.
- Only online b/a can use CheckoutAPI so when requesting to create new Checkout, it will automatically try to register the billing account to provider if it is offline
- DelegatedCheckout with virtual credits can be used with offline customers
- Offline customers will not interact with billing provider at all and can't support subscriptions as well
- A offline customer can be migrated to online using RegisterBillingAccount API
- feat(frontier): create billing account without billing provider proton#360
- A change in frontier env/yaml configs are introduced to handle offline accounts better
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
Pull Request Test Coverage Report for Build 9381349099Details
💛 - Coveralls |
Pull Request Test Coverage Report for Build 9402997861Details
💛 - Coveralls |
Pull Request Test Coverage Report for Build 9402923486Details
💛 - Coveralls |
- Offline billing accounts are not registered in billing provider like Stripe by default. - Only online b/a can use CheckoutAPI so when requesting to create new Checkout, it will automatically try to register the billing account to provider if it is offline - DelegatedCheckout with virtual credits can be used with offline customers - Offline customers will not interact with billing provider at all and can't support subscriptions as well - A offline customer can be migrated to online using RegisterBillingAccount API - raystack/proton#360 - A change in frontier env/yaml configs are introduced to handle offline accounts better ```yaml billing: # default currency to be used for billing if not provided by the user # e.g. usd, inr, eur default_currency: "inr" # billing customer account configuration customer: # automatically create a default customer account when an org is created auto_create_with_org: true # name of the plan that should be used subscribed automatically when the org is created # it also automatically creates an empty billing account under the org default_plan: "" # default offline status for the customer account, if true the customer account # will not be registered in billing provider default_offline: false # free credits to be added to the customer account when created as a part of the org onboard_credits_with_org: 0 ``` Signed-off-by: Kush Sharma <thekushsharma@gmail.com>
Pull Request Test Coverage Report for Build 9417411053Details
💛 - Coveralls |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.