I would need your Stripe payment extension for Magento 2 CE enabled only for selected customer groups and only for selected product attribute sets

smatric · May 23, 2018, 2:23am

Hi Dmitry.

I would need your Stripe payment extension for Magento 2 CE enabled only for selected customer groups and only for selected product attribute sets.

Would you be interested in adding that functionality to your extension? If so, how much would you charge for that?

Mateusz

dmitrii_fediuk · May 23, 2018, 5:52am

I can implement it for $199 as a separate module (without the Stripe module modifications).
Of course, I should buy a licence for the Stripe module too.
You can order my service og Upwork: upwork.com/fl/mage2pro.

smatric · May 24, 2018, 5:41am

I would also need one more customization. I need to assign different shipping cost (including a free option) based on attribute set. How much would you charge for that?

dmitrii_fediuk · May 24, 2018, 9:44am

How is your new customization related to Stripe exactly?

smatric · May 24, 2018, 2:28pm

It’s not. It would we a separate extension. I’m asking if you’re interested in extra work.

I would need two custom-written extensions:

A Stripe payment gateway that can be enabled/disabled per customer group and per attribute type
A shipping module that can be enabled/disabled per customer group.

dmitrii_fediuk · May 24, 2018, 8:17pm

What does mean “per attribute type”?

smatric · May 24, 2018, 8:29pm

Sorry, I meant attribute set.

dmitrii_fediuk · May 24, 2018, 8:30pm

What does mean “enable a module per attribute set” exactly?

smatric · May 24, 2018, 8:39pm

We sell products to both dealers and retail customers. But not all of them. Some products, for example scooters, can only be sold to dealers. Others, such as bicycles, can be sold to both dealers and to retail customers. Dealers never have to pay at the checkout. They use “To Be Billed” payment options, whereas customers, if allowed to purchase a given product, have to pay right away.

Here is a table that may help you understand it:

dmitrii_fediuk · May 24, 2018, 9:04pm

Provide me a use case when the Stripe payment option is eligible for the group of the current customer, but is not eligible for an ordered product.

smatric · May 25, 2018, 5:21am

If a retail customer added a scooter to cart, they would not be allowed to use Stripe’s payment gateway.

On the other hand, if a retail customer wanted to purchase a bicycle, the payment would be available to him or her.

smatric · May 25, 2018, 5:22am

Btw. you can email me directly at sobczak.mateusz@gmail.com, if that’s easier for you.

dmitrii_fediuk · May 25, 2018, 8:50am

OK, I can implement the Stripe payment module restriction per a customer group and per an attribute set for $250.

smatric · May 25, 2018, 3:26pm

Alright.

When you build the new extension, please build it as a single extension, not 20 or 30 separate extensions that make a mess:

Also, please make sure there is no exceptions:


[2018-05-23 02:08:56] main.CRITICAL: Magento\Framework\Exception\LocalizedException: Class Magento\Customer\Block\Address\Renderer\AbstractAddress does not exist in /var/www/html/vendor/magento/framework/Code/Generator.php:103
Stack trace:
#0 /var/www/html/vendor/magento/framework/Code/Generator/Autoloader.php(35): Magento\Framework\Code\Generator->generateClass('Magento\\Custome...')
#1 [internal function]: Magento\Framework\Code\Generator\Autoloader->load('Magento\\Custome...')
#2 [internal function]: spl_autoload_call('Magento\\Custome...')
...
#16 /var/www/html/vendor/mage2pro/core/Sales/Plugin/Model/Order/Address/Renderer.php(99): Magento\Sales\Model\Order\Address\Renderer\Interceptor->Magento\Framework\Interception\{closure}(Object(Magento\Sales\Model\Order\Address\Interceptor), 'html')
#17 /var/www/html/var/generation/Df/Sales/Plugin/Model/Order/Address/Renderer/Interceptor.php(23): Df\Sales\Plugin\Model\Order\Address\Renderer->aroundFormat(Object(Magento\Sales\Model\Order\Address\Renderer\Interceptor), Object(Closure), Object(Magento\Sales\Model\Order\Address\Interceptor), 'html')
#18 [internal function]: Df\Sales\Plugin\Model\Order\Address\Renderer\Interceptor->aroundFormat(Object(Magento\Sales\Model\Order\Address\Renderer\Interceptor), Object(Closure), Object(Magento\Sales\Model\Order\Address\Interceptor), 'html')

dmitrii_fediuk · May 25, 2018, 5:36pm

No, I will not change the structure of my modules.

smatric · May 25, 2018, 6:49pm

That’s too bad. It’s a lot of clicking to enable/disable your module. And it makes it harder going through the list to find other modules.

I want to make sure we’re on the same page. Your payment module will allow me to to create a list of rules when the payment should be enabled, correct? I imagine an interface like this:

Can you also add another table like this, with same interface for adding rules and call it “To Be Billed”? This would not process any payments. It would allow completing an order without paying, and say that the customer will be contacted later regarding paying for the order.

dmitrii_fediuk · May 25, 2018, 7:03pm

$250 is the price for a predefined rule set.
If you need a backend interface with an ability to apply an arbitrary rule set as in your screenshot above, the implementation price will be doubled: $500.

smatric · May 25, 2018, 7:18pm

That’s getting expensive. Can you at least add a textarea in the backend where I can put numbers like this:

3, 13;
3, 21;

?

Oh, and we’re using Magento 2.0

smatric · May 28, 2018, 5:10am

When can you have the extension ready?
If it’s going to take more than a week, I may have to look for other options.

dmitrii_fediuk · May 28, 2018, 5:43am

The extension is ready and widely used.
I just currently do not have time for low-paid custom work.