- composer name:
aligent/braintree-orocommerce
This bundle allows you to use the Braintree Drop In UI with OroCommerce.
-
Install this module via Composer
composer require aligent/braintree-orocommerce
-
Clear cache
php bin/console cache:clear --env=prod
-
Run Migrations
php bin/console oro:migration:load --force --env=prod
-
Install Assets
php bin/console assets:install --env=prod
-
Build Assets
php bin/console oro:assets:build --env=prod
Go to the "System -> Integrations -> Manage integrations" and click "Create Integration". Select "Braintree" as the integration type and fill all required fields.
To Enable select the Enabled checkbox in the PayPal section and add values for all fields. Note: Your Braintree account must be setup to accept PayPal payments see here: https://articles.braintreepayments.com/guides/payment-methods/paypal/setup-guide for more details.
Once complete you must now create an appropriate 'Payment Rule' see: https://doc.oroinc.com/user/back-office/system/payment-rules/#sys-payment-rules for more details.
Current:
- PayPal
- Credit Card
Coming Soon:
- Google Pay
- Apple Pay
- PayPal Credit
- Venmo
Currently, this bundle only supports the 'Purchase' action, 'Validate' and 'Capture' are coming soon.
BraintreePaymentActionEvent (aligent_braintree.payment_action.{action}):
This event is fired when a payment action executes but before the payload is sent to the payment gateway. It is used internally to build up the payment payload and can be extended with other listeners to add data to be sent to the payment gateway.
Currently supported events:
- aligent_braintree.payment_action.purchase
Custom payment actions can be added by implementing the BraintreeActionInterface and then tagging the service with:
{ name: braintree.action, action: action_name }
If you have any issues with this bundle, please feel free to open GitHub issue with version and steps to reproduce.
Any contribution is highly appreciated. The best way to contribute code is to open a pull request on GitHub.
Adam Hall [email protected].
(C) 2020 Aligent Consulting