View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 1626 | Composr | ecommerce | public | 2014-04-22 12:33 | 2022-10-27 21:02 |
| Reporter | Chris Graham | Assigned To | Chris Graham | ||
| Priority | normal | Severity | feature | ||
| Status | resolved | Resolution | fixed | ||
| Summary | 1626: Payment gateway: CCBill | ||||
| Description | ^ | ||||
| Tags | No tags attached. | ||||
| Attach Tags | |||||
| Time estimation (hours) | 10 | ||||
| Sponsorship open | |||||
|
|
If sponsored could it be built as a non-bundled add-on that can be easily installed like some of the other non-bundled add-ons? This would allow it to be installed when needed and ignored where not needed and avoid bloating the core system. |
|
|
It would definitely be worth while having an alternate to PayPal as the PayPal organisation has to be the most unhelpful, difficult, unable to communicate with and downright useless payments gateway there is. How they got to be so big is quite beyond me. We would sponsor something here Chris and Australia Post use GIRO which could be an added bonus. Its probably premature to leap into this while v10 is getting traction but if there is some specification being written up and it will link to things like existing shopping cart, paid membership group etc. then worth doing. |
|
|
I have not had as bad an experience with PayPal myself, however, one of the websites I have setup is designed to have content which excludes PayPal as a payment processor due to their ToS. So need to look to alternates. |
|
|
I believe we implemented CCBill for a client but have not had a chance to merge the code in yet. "If sponsored could it be built as a non-bundled add-on that can be easily installed like some of the other non-bundled add-ons? This would allow it to be installed when needed and ignored where not needed and avoid bloating the core system." The approach we have taken with the payment gateways is sharing a common set of options to configure them so that the only bloat is in a single drop-down for choosing the gateway to use. Modularising each individual driver wouldn't be out of the question, but I'd rather avoid the extra architecture complexity involved in that until we get to e.g. having 15 of them. Regarding PayPal vs other gateways... PayPal do have a bad reputation for being a pain, but at the end of the day this is largely due to massive attempt at fraud that they're constantly embattled with, and possibly also political interference from the US government. All the scam artists in the online world flood through these payment providers because of the very low barrier to entry. A lot of companies tried to compete with PayPal but never found any growth, I think because they found all their resources ended up tackling similar fraud issues. When it comes to the other services tied directly to bank accounts (credit card processing front ends and merchant bank accounts), there is a higher barrier to entry. That is the trade-off. You typically need to pay the bank for a special account, and jump through all kinds of hoops. |
|
|
ccbill: No application needed: No Transparent pricing: Yes No monthly fee: Yes Reasonable per-transaction percentages: No (3.9% - 10.8%) No bad reputation: Yes Targets micro businesses: Yes Payment button+IPN API: Yes (https://ccbill.com/doc/dynamic-pricing-user-guide) Local payments API: Yes (https://ccbill.com/doc/ccbill-restful-transaction-api) Reasonably modern website: Yes Reasonably stable business: Yes International: Yes No bank merchant account needed: Yes Supports subscriptions: Yes Supported by PHP Omnipay library: No |
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2022-10-27 21:02 | Chris Graham | Note Added: 0007595 |
