6

You must create a module and a module action. There are docs here. The key is to grant your action a CSRF exemption, like so: ee()->db->insert('actions', array( 'class' => 'Module_name' , 'method' => 'method_to_call', 'csrf_exempt' => 1, )); Look up the action_id in the exp_actions table for your newly created action. Your action can ...


4

I'm the developer of Charge so this is obviously biased. Charge works great for member subscriptions. The focus with Charge is to keep it as simple and rock solid for the developer and customer as possible. To that end - it's tied directly to using Stripe as the payment gateway. Understandably that's not going to be perfect for every project. I'm in the ...


4

Let me first start by saying you should not store users' credit cards data on your servers under any circumstance. True PCI compliance is super expensive to initially setup and to maintain. Having said that I am not familiar with PayU's API but I can speak from other payment gateway experience. If your payment gateway supports the feature you will want to ...


3

I would advise that you built it into an Omnipay gateway. Omnipay is the payment provider library that powers Exp:resso Store 2 and so by building it for Omnipay it will work on Store. They have a GitHub with examples and documentation https://github.com/omnipay/omnipay If you decide to go down that route, the ExpressionEngine Answers website wouldn't be ...


3

The issuers field was missing from Store 2, and this has recently been fixed in Store 2.1. From the release notes: Added {gateway_name:issuer_options} variables for gateways which provide a list of issuers The Mollie-specific documentation needs updating, but the correct syntax for the issuers variable in Store 2 is {gateway_name:issuer_options}. So you ...


3

No e-commerce modules available for EE currently come bundled with Braintree gateway plugins, but all support the development of custom gateways. So I'd choose your module based on the features you need, then tackle the Braintree gateway after.


3

When it comes to supporting TLS 1.2, generally this is a server-side change, not a script-based change. So there's no action needed on DevDemon's part. Simply ask your host if they support TLS 1.2. (Also, Store does not use Stripe's PHP library - they make more "bare-metal" calls to the API.) You can test it yourself by following Stripe's notes here.


2

If this is in reference to Store v2 then the good news is that support for the Realex payment gateway is intended to be rolled out in the next month or two. Keep an eye on the release notes for confirmation of when it's been added to the available gateways.


2

Is your site available to the outside world (system is on and no passwords or funny business preventing people from accessing your test site?). Have you followed the instructions here? https://exp-resso.com/docs/payment_gateways.html#worldpay You need to make sure the payment response URL in WorldPay is set to <wpdisplay item=MC_callback>. Also, ...


2

PayPal has depreciated the PayPal Standard API which requires the use of their IPN (Instant Payment Notification) system which has been awful for as along as I can remember (and often causes orders to not complete since the IPN never gets sent). I would enable the PayPal Express gateway in Store > Settings > Payments Methods then Add New Payment Method ...


2

This issue is most likely being caused by either your secret word not matching or expresso store is not setup to validate the hash on demo sales. When placing 2Checkout demo sales, the MD5 hash returned by 2Checkout is intentionally broken by computing the hash with a 1 in place of the order_number so if you are checking against the hash your return script ...


2

Currently there are only 2 subscription modules that I know that you could transition to now that it looks like Membrr/OpenGateway are no longer going to be supported. Both options require a fair bit of work from you to handle the migration of content and subscriptions over but are probably better options then keeping a dead piece of software running your e-...


2

You need to specify the return and cancel URLs on a per-request basis. In Store v1 you can get these URLs with: $this->param('return_url'); // use this for success and error $this->param('cancel_url'); // use this for cancel You can see how this is done in other gateways such as PayPal Express: https://github.com/expressodev/ci-merchant/blob/master/...


2

Ideally you should use them to create a plugin but technically you can place them wherever you wish so long as whatever needs to reference them can reach them.


2

As Justin mentioned, if PayU supports this then it would certainly be possible. Store (and the payment library Omnipay) supports both on-site and off-site gateways fine, so it's just a case of whether or not PayU supports this at their API level.


2

I am not familiar with the PayU API but it shouldn't be a problem if their API allows on-site integration of Discovery Miles. You will just need to write a custom gateway that handles it based upon their API. Store's gateways are built on top of Omnipay ( https://github.com/omnipay/omnipay ) and you should be able to look at the include gateways as examples ...


2

PayU should be able to provide you with dummy credit card test details so you can test the whole process start to finish.


2

If PayU support payment by Discovery Card (and it looks like they do) then you just need to implement a payment gateway for PayU and PayU will automatically provide that as a payment option presented to customers. Discovery Miles is the currency earned when customer makes a payment with their Discovery Card and that again is handled automatically by the ...


2

Just to expand on Justin's answer a little, payment gateways in Store 2.1 can now be registered as separate extensions. This means you don't need to copy anything into the third_party/store folder or worry about re-copying files when you upgrade. The extension hook you need to use is called store_payment_gateways. If you are unfamiliar with ExpressionEngine ...


2

As of Store 2.1 gateways are now added as separate extensions outside of the actual Store folders. This makes it easier in the future to upgrade Store because you don't have to worry about overwriting your custom gateway. (Last item under Developer). You can see an example of the folder structure in the example gateway Store Check.


2

I assume you are using Store > 2. If that is the case you would be making your own extension. Store has a default layout for these extensions available on github here. If you notice in the ext.store_check.php file, there are these lines. // tell PHP where to find the gateway classes // Store will automatically include your files when they are ...


2

The most simple solution in case like this: Reboot the server.


2

This is not currently possible with Store - the way Omnipay is integrated with its abstracted settings methods it only looks in the database. A good feature request for Vector though! (Likewise for CartThrob.)


1

Hein Please look at this Omnipay with 3D secure as a point of reference; as each gateway will require that the Secure 3D process be implemented differently and as such the payment process steps for the module will have to be applied in this manner. In the case of PayU MEA, 3D Secure (Enterprise API) is a good reference.


1

These errors are caused by PHP namespaces. Because your gateway is in the Omnipay\PayU\Message\ namespace, if you call new SimpleXMLElement() then PHP will look for the Omnipay\PayU\Message\SimpleXMLElement class, which obviously doesn't exist. To prevent this error, you either need to add use SimpleXMLElement; at the top of your PHP file, or you can add a ...


1

Unfortunately we've not had time to implement it for Store v2 as of yet. There are a few complications with that gateway that we found out about when building integration with Store v1. For that reason it took a bit more work than the others and as of yet we haven't had a chance to build a gateway extension for it. A few people have mentioned they'd be ...


1

Have you updated Matrix & EE yet? It's not a Cartthrob issue i'm afraid.


1

This was an issue with accepting tokens with a test gateway. This has now been resolved.


1

One or two people have enquired about it but I haven't seen or heard of any completed gateways for Paybox as of yet. If you're looking to create your own then feel free to look at Store Check to get an idea of how that gateway is put together and integrated as it's own extension. The other gateways that ship with Store will also provide a good starting ...


1

Adding an input for language to your checkout form should set paypal's localecode. <input type="hidden" name="language" value="DE" />


Only top voted, non community-wiki answers of a minimum length are eligible