Welcome to the Paymentlib for Commerce page¶
This extension expect you to have installed paymentlib and at least one payment provider
- Version 0.1.3 (current)
More bug fixes along and the first release to TER, should be suitable for non programmers to use. Step 3: Payment is now changable, and can be placed after Step 4: Check your details ( but remeber to change the step numbers in the translation files )
- Version 0.1.2
Mostly bug fixes for 0.1.1 along with some localization
- Version 0.1.1
This release is mostly intended for programmers, while it can be used for production it is not advisable to do so as most strings are hard coded at this time. Future releases will have all such texts in popper locallang.xml files, but this has currently taken a backseat to solving the problems caused by commerce's rather odd payment flow.
Anoyances this release¶
The payment flow in Commerce goes against good trading customs ( and I'm fairly sure danish law ), the flow is ( as per the "class.tx_commerce_payment_creditcard.php" example )
1 " Billing Adress "
2 " Delivery Adress " (Optional)
3 " Payment "
In this step the customer enters his/her credit card details, it remains unclear wether or not the example is meant to actually withdraw the money here.
4 " Check your details "
This page show you an overview of what you are buying, total sum you are paying and asks you to accept the terms and conditions as set foward by the shop
5 " Finish "
Shows you a copy of the order confirmation sendt to you
The problem with that is that we are asking for credit card details before the customer is show what they are paying for and before they can accept the terms and condition for buying the goods/services.
As we are validating the card at the "payment" step above it is probable that the actual withdrawal also occurs here, and if not we are storing their credit card information for later use ( after they have accepted the terms and conditions ) which is a problem in it self.
Payment flow fix
As a plugin we don't have much control over the payment flow, so we cannot swap step 3 & 4 to fix the flow.
Instead we are locked in the predetermined flow, but we are still free to make a few changes
Step 3 now is been reduced to where we choose which payment method to use ( typically which credit card )
Step 5 now contains the actual payment step, it will insert the form provided by paymentlib here, and once we are informed that the payment has succeeded step 5 works like before.