dsyo9700
2019-01-04 08:25
浏览 48
已采纳

Symfony 4 - 设置Braintree Payments集成

I am trying to set up Braintree integration in my Symfony 4 PHP app.

I have used composer to require and install the latest version of Braintree SDK, and have added testing credentials to env file.

Set Up Client

https://developers.braintreepayments.com/start/hello-client/javascript/v3

I then added the client code to my twig template for Drop-in UI.

<div id="dropin-container"></div>
<button id="submit-button">Request payment method</button>
<script>
 var button = document.querySelector('#submit-button');

 braintree.dropin.create({
  authorization: 'CLIENT_TOKEN_FROM_SERVER',
  container: '#dropin-container'
 }, function (createErr, instance) {
  button.addEventListener('click', function () {
   instance.requestPaymentMethod(function (err, payload) {
     // Submit payload.nonce to your server
   });
  });
 });
</script>

And included this script in the js block

<script src="https://js.braintreegateway.com/web/dropin/1.14.1/js/dropin.min.js"></script>

Set Up Server

https://developers.braintreepayments.com/start/hello-server/php

Next step is to generate a client token

$clientToken = $gateway->clientToken()->generate([
    "customerId" => $aCustomerId
]);

and then send token to client etc.

Question

My question is where do I put the server side code in my Symfony 4 app?

Do you create a Braintree.php service in src/Services and put all the Braintree PHP code in there or in the controller, or some in both?

  • 写回答
  • 好问题 提建议
  • 关注问题
  • 收藏
  • 邀请回答

1条回答 默认 最新

  • dornc9470 2019-01-04 09:21
    已采纳

    Best practice is to keep Controllers as thin as possible. Controller method should:

    • accept the request
    • call the appropriate service
    • handle response

    This is all a controller should be responsible of. In your case, the appropriate service would be your BraintreeService, a class responsible for whatever you need to do with Braintree SDK or anything related to Braintree.

    Symfony follows the philosophy of "thin controllers and fat models". This means that controllers should hold just the thin layer of glue-code needed to coordinate the different parts of the application.

    https://symfony.com/doc/current/best_practices/controllers.html

    已采纳该答案
    评论
    解决 无用
    打赏 举报

相关推荐 更多相似问题