![bill4time payment method list add method bill4time payment method list add method](https://i.ytimg.com/vi/OKhlvaDkkUY/maxresdefault.jpg)
![bill4time payment method list add method bill4time payment method list add method](https://www.dhresource.com/0x0/f2/albu/g2/M01/42/80/rBVaG1orm6CAIuEMAAFoGK8wLs8192.jpg)
You won't see any form tags or submit buttons in the additional details form, however, because this is handled autmomatically by concrete5, by a method in the controller file. When configuring the default gateway through the dashboard, you'll see the contents of the additional details form, which are simply some concrete5 configuration form elements with names like "PAYMENT_METHOD_DEFAULT_EMAIL_RECEIPT" and "PAYMENT_METHOD_DEFAULT_TRANSACTION_TYPE". It does not send any information to any third parties or validate a payment request in any way. The default payment gateway is simply a way to checkout easily through your concrete5 eCommerce installation. Rather than go through these one by one, it's easiest to look at how all three components interact, by going through two examples of payment gateways that come with the eCommerce addon. If it exists, it is named "method_form.php" This is displayed to site administrators when they wish to enable or disable the payment method, if the payment method requires additional information. The additional details form for this payment method. This is named "form.php" and is displayed to the user after they have chosen this payment method for checkout (or, in the case that this is the only payment method available, when the user has entered their shipping information.) This file is required. The checkout form for this payment method. The class must extend the CoreCommercePaymentController class. It must begin with "CoreCommerce", then contain the camel-cased name of the payment method, and finish ith "Payment MethodController." If your payment method is named "my_website", your class would be CoreCommerceMyWebsitePaymentMethodController. Like blocks or other items in concrete5, the controller class must be named appropriately. The controller file, named "controller.php" This file is required. These are all files that exist within the directory you created for your specific payment method. There are several items that comprise a payment method. For example, the handle of our Paypal Website Payments Standard payment method is "paypal_website_payments_standard."Ĭreate a directory with the same name as your payment method's handle in the local payment methods directory (referenced above.) This should be descriptive, but be all lowercase and contain no spaces.
![bill4time payment method list add method bill4time payment method list add method](https://help.moosend.com/hc/article_attachments/360046660313/How_can_I_add_a_new_payment_method_stepa4.png)
This is a short name that will match the directory that your payment method resides in.
#Bill4time payment method list add method code#
Creating the Payment Method Directoryīefore you can write code for your payment method, you will need to:Ĭhoose a handle for your payment method. This is your website's local payment methods directory, and will be referred to as such from within this tutorial. From the root of your concrete5 install, the path to this directory should be Within this directory, create a "payment" directory, and within this, create a "methods" directory.
![bill4time payment method list add method bill4time payment method list add method](https://www.onu.edu/sites/default/files/controller-add-payment-method.png)
You'll need to create a directory named "core_commerce" in the models/ directory, at the root of your concrete5 install. NOTE: We integrate with two separate API's for, one that takes your credit card details on your own website and one that sends you to to fill in your details.