Creator of the Monero Subscriptions Wallet here.
I’ve been thinking about it, and I want to add a few things in the monero-subscription code protocol. Originally, I imagined it just being for subscriptions but I’d like it to work for:
- recurring subscriptions (good until canceled)
- subscriptions with a set number of payments (then auto-cancel)
- one-time payments
The ultimate vision is:
-
Merchant creates a unique Monero Payment Code and gives it to you on their website (all the info about the transaction, along with instructions to “use this payment_id when you pay me” [so that they know YOU paid them and not another customer]. The payment_id is only visible to you and the merchant using Monero integrated addresses ).
-
Monero Subscriptions Wallet (takes Monero Payment Codes and can pay them based on the details specified in them)
-
Monero Business Wallet (for merchants to recieve these payments, and record the payment amounts [in XMR, USD value of the payment at time of reciept, payment_id, etc.], and auto-forward to cold storage/auto-convert to stable coins. (As an internet-connected hot wallet, the Business Wallet is not intended to hold funds for more than a few minutes.)
NOTE: I know some people in this group are super against stable coins, and I understand why and agree. I’m a big fan of the Monero circular economy, but I believe that this will help a lot with accessability. A lot of merchants will accept crypto of any kind “if it’s easy”. Auto-convert to stable coins helps merchants lock-in the value (no price fluctuations) and makes it easier to sell on more exchanges. I would love for merchants to keep it as Monero, but some will want to sell it for fiat, so the business wallet will provide both options.
Because “Monero Subscription Codes” will now also include the ability to do “one-time payments” and “set-number of payments” (in addition to “recurring until canceled” subscriptions), I think it’d make sense to change the name from “Monero Subscription Codes” to “Monero Payment Codes”. What does the community think of this idea?
I think it states what it does better, but I also wouldn’t want to cause any confusion between “wallet address” vs. “Monero Payment Code”. Thoughts, or alternate name suggestions are welcome!
I would like to be able to dedicate more time to working on this, but right now I am only working on it when I have extra time (which is why development has been slow). I created a CCS for the Monero Business Wallet, but it was “declined”, so people are “not allowed” to donate to the development. If you would like to donate directly (Monero/BTC/Cashapp/Credit Card) you can do so on the Monero Business Wallet Github. Just scroll down to the donate section.
P.S. If you know Python and would like to help, but are thinking to yourself “I’m probably not qualified to help”, you are definitely qualified to help. Just shoot me a message. I’d love to have more help with this.
@lukeprofits I think your application can be better described as “payment scheduler”, and you’re right about “monero payment code” sounding confusing. Maybe “monero scheduler code”? Or “monero payment request”?
Also, I’m still interested in implementing code generation in my project. The only blockers are portability issues that I previously reported.
Thanks for all the suggestions you put on it on Github. I plan to implement all of them, but I want to figure out the name before adding the versioning system, and all the other changes. Since it’s for more than just subscriptions, and will be (I think) the easiest way to accept payments as a merchant, I don’t want it to have a confusing name.
“Monero Payment Request” is pretty good. That sounds pretty different from a wallet address and could include subscriptions and one-time payments.
