This repository has been archived by the owner on Nov 30, 2022. It is now read-only.
-
-
Notifications
You must be signed in to change notification settings - Fork 374
Billing Built-In #8
Labels
feature
Enhancement to the code
Comments
Branch reference: billable-feature. |
So far:
Next:
|
Billing controller is now complete. Need to add tests for the processor action in the controller which completes things. After that, some real-world tests. |
Tests are now complete, code is also completed. Working on updating some docs, and will begin real-world tests hopefully tomorrow, if not, early next week. |
Based on tests (both code and real-world), we're good to merge in master. From here, i'll update docs/wiki, do more tests, and release |
Merged
Closing due to PR #10 |
Closed
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
I'm going to build in the ability to charge for apps. I've done this many times, and figure its good to bake in as an (optional) thing for this package.
I plan on making it a separate middleware which anyone can attach to their routes. All settings for the billing including app name, pricing, trial period, etc, will be configurable.
Essentially the flow will be:
i. Redirect to Shopify billing screen
ii. Shop accepts/declines and is redirected back to a billing controller
iii. If accepted, charge is activated and stored in database for that shop, then redirected to home route.
iiii. If declined, show error
i. Continue to route as normal
I'll be working on this in a new branch, with tests, and merge in once I feel its OK. Timeline for this is a bit sparse as I'm a tad busy these days so hang tight :)
The text was updated successfully, but these errors were encountered: