Activity Feed
Sort by
C
Contact
Having worked with ecommerce + strapi:
Many payment providers have a few dozen variables to accept to charge a single payment. (they take info like tax amount, rate, order items, order item variations, etc, etc) because they use this data for accounting. The actual implementation of a wide variety of payment providers relies on having access to these variables. Given the nature of how developers use strapi the configuration page for even one provider would be pretty complex, not even taking into account having to create a "universal" system that can support multiple. You also need to ensure you're passing values into payment provider apis as certain data types because most of them are explicitly typed using SOAP apis. There are a lot of different requirements for each payment provider and having to ensure that whatever custom content-type has all the values necessary is a huge hurdle all on it's own.
Personally I think payment plugins should be created (providing a place to have a basic config ready to go) but they should leave 90% of the full implementation to the developer because there are a lot of moving parts and, usually, additional custom business logic involved with accepting payments (creating an order as a result of a successful payment for example).
A centralized system for this would be GREAT but I feel it will just be nothing more than a wrapper that wraps a wrapper, wrapping a wrapper of an old SOAP api. Which to me seems like a maintainability nightmare.
The actual implementation of each provider is really straightforward when working with node directly: typically charge(40+variables) refund(id) etc making the tradeoff here pretty one sided. I've personally implemented a couple different payment providers with strapi and it took ~10 hours including testing.
Just my two cents
D
Davidjeba D
Name it "PayStack"
1.Stripe, Worldpay, ApplePay, AmazonPay, GooglePay, etc
2.Coingate, Coinsgate, Bitpay etc
Payment Modes
1.Fullpayment
2.Pre-Payment
3.Partial Payment
4.Recurring Payment
5.Split Payment [Multi-User]
6.Crowdpayment
7.Pay to Multi Accounts etc
Emilie Ringwald
Stripe collaboration for payments for stores 😁