A bit of theory: You messed to different ways of using Payum. First one is completely custom (other words payment specific format). In this case you can use whatever that implements \ArrayAccess interface. The fields names and their values looks same as they are in Paypal docs. The other way...
php,symfony2,stripe-payments,payum
Stripe Checkout is designed this way. You see the button click it, fill all the required info and that's it. If you want to fill credit card details earlier you can do that, but in that case you have to use Stripe "direct". Implemented in Omnipay and used via Omnipay...
The main problem is described here: https://github.com/Payum/Payum/issues/233. Long story short: There was a security bug in SSL and PayPal desided to disable old version and allow only new one. They did a BC break. Here you may find some additional info: https://github.com/Payum/Payum/issues/250, https://github.com/Payum/Payum/pull/237...
php,symfony2,paypal,payment-gateway,payum
I finally managed to get it done. I needed 4 files PaymentController Orders (Entity) PaymentToken (Entity) Orders (Model) This is my PaymentController looks like <?php namespace ClickTeck\featuresBundle\Controller; use ClickTeck\featuresBundle\Entity\Orders; use Symfony\Bundle\FrameworkBundle\Controller\Controller; use Payum\Paypal\ExpressCheckout\Nvp\Api; use Payum\Core\Registry\RegistryInterface; use Payum\Core\Request\GetHumanStatus; use Payum\Core\Security\GenericTokenFactoryInterface; use...
php,symfony2,loops,paypal,payum
You just need to loop through the items to generate that portion of the API request dynamically. So it would be something like this. $i = 0; foreach($orderDetails as $orderItem) { $paymentDetails['L_PAYMENTREQUEST_0_ITEMCATEGORY' . $i] = Api::PAYMENTREQUEST_ITERMCATEGORY_DIGITAL; $paymentDetails['L_PAYMENTREQUEST_0_AMT' . $i] = $orderItem['price']; $paymentDetails['L_PAYMENTREQUEST_0_NAME' . $i] = $orderItem['name']; $paymentDetails['L_PAYMENTREQUEST_0_DESC' . $i] =...
Account restricted means that PayPal has flagged the account involved as problematic and is preventing it from processing transactions. It could be suspected of beig compromised (stolen credentials), or it could be suspected of being a fraudulent account, or many other things. If it is your account you can log...
php,symfony2,curl,paypal,payum
You can overwrite the service payum.buzz.client. Just define it in your bundle which is registered after PayumBundle. <service id="payum.buzz.client" class="Buzz\Client\ClientInterface" factory-class="Payum\Core\Bridge\Buzz\ClientFactory" factory- method="createCurl"> <call method="setVerifyPeer"> <argument>false</argument> </call> </service> or in yml services: payum.buzz.client: class: Buzz\Client\ClientInterface factory_class: Payum\Core\Bridge\Buzz\ClientFactory factory_method: createCurl...