Payments; monetize your community

wolfshards

There a way to add support like Paypal, Square and more?

luceos

wolfshards allowing many more payment providers is a huge task.

Providers can never be removed as subscribers rely on them.
Api's to these payment providers change regularly.
Each of these payment providers have their own implementation.
Paypal is one of the most horrible payment providers to implement and each has their own quirks.

Some payment providers bundle many regularly used payment methods like Stripe, one of those is Paddle. Don't pin me on this, but I do have plans to make the Stripe integration more flexible so that more payment methods can be easily added.

Darkle thank you, this warms my heart 🥰

luceos

Stripe now also supports PayPal, some restrictions might apply on their end.

cc Braden ART994 wolfshards who asked about it.

To celebrate this, you can get a copy of Payments and all future versions for a lifetime fee of $ 77,77. Only two copies are available, go here: https://extiverse.com/extension/blomstra/payments?key=retrograde-protostar-orbit-kepler.

jbstore

thanks for your awesome works.
will you be kind enough to add bitcoin ?

luceos

jbstore that's not likely to happen soon, no. Stripe actually had Bitcoin support but gave up on it in 2018.

Spooonky

Hey could someone help me with that error?

composer require blomstra/payments

  [InvalidArgumentException]
  Could not find a matching version of package blomstra/payments. Check the package spelling, your version constraint and that the package is available in a stability which m
  atches your minimum-stability (stable).

luceos

Spooonky did you follow the instructions from https://extiverse.com/premium/subscriptions to set up the token and repositories.extiverse entry?

Spooonky

luceos THX Worked

TOWUK_ru

Can I get forever given an extension or a simple version or functionality?

luceos

TOWUK_ru I'm sorry, can you clarify your question?

TOWUK_ru

luceos This extension is good, but I would like to get rid of the paid subscription in favor of the purchase for your forum, and if you feel more accurate to buy and use anything else, pay and use anyone once, or some kind of analogue is free with simple feature

luceos

TOWUK_ru the question is, does your comment relate to a) the subscription from extiverse to acquire the extension or does it relate to b) the subscriptions you are able to set up on your community using this extension.

a) reach out to me I might still have some unused lifetime (pay once) licenses available for a pretty price (either discord or email works, see OP)
b) all payment modes of this extension support single pay options

louanbastos

luceos Do you still have lifetime licenses?

luceos

louanbastos I do, contact me on discord or send an email to helpdesk@blomstra.net, I'll get back to you as soon as I can.

wero-dev

我想知道 , 它可以用在flarum 1.1.1吗

luceos

wero-dev I don't understand you. If you're wondering whether this extrnsion works with flarum 1.1.1, it does. If you encounter any issues I'll fix them.

wero-dev

luceos Please check your email, I sent you a consultation email

ART994

great solution, it's a pity that there are no other payment systems

luceos

I'm working on a new release, see https://blomstra.community/d/130-developer-logbook-payments

When the new version is completed, the price for this extension goes up and we'll probably move to a yearly plan now that Flarum reached stable.

ivan006

im getting the below composer error

$ composer require blomstra/pay
Warning from https://repo.packagist.org: Support for Composer 1 is deprecated and some packages will not be available. You should upgrade to Composer 2. See https://blog.packagist.com/deprecating-composer-1-support/
./composer.json has been updated
Loading composer repositories with package information
Warning from https://repo.packagist.org: Support for Composer 1 is deprecated and some packages will not be available. You should upgrade to Composer 2. See https://blog.packagist.com/deprecating-composer-1-support/
Updating dependencies (including require-dev)

Fatal error: Allowed memory size of 1610612736 bytes exhausted (tried to allocate 4096 bytes) in phar:///usr/bin/composer/src/Composer/DependencyResolver/RuleWatchGraph.php on line 52

Check https://getcomposer.org/doc/articles/troubleshooting.md#memory-limit-errors for more info on how to handle out of memory errors.bluegpyuty@www404:~/yellow.bluegemify.co.za_app$

luceos

ivan006 yeah, we talked about this on discord. Composer v1 requires a lot of memory, so either increase that (during cli/bash usage this is usually unlimited) and/or upgrade Composer to v2 (which I recommend anyhow).

« Previous Page Next Page »