IsanyoneworkingonaBraintreemodule?

Makes sense to me.  If Braintree
only offers official support via their SDK,
then that's what we should use.
 
Currently we're using a kludgy home-grown
interface on top of the Braintree SDK, so
it would be nice to have a consistent Omnipay
interface.  We use a lot of special
Braintree functions (like escrow, submerchants,
etc) that aren't provided by most processors,
so someone will need to figure out how to
map those to Omnipay methods.  If I
have some time, maybe I can work on that
and help out.
 

Yeah,
but I don't think the HTTP API is really
exposed. They are just >>
  offering their PHP (or other
languages) SDK libraries, not their REST >>
  API.  >>   See
https://www.braintreepayments.com/blog/when-rest-isnt-good-enough/ >>
  (didn't find a recent update)
 >>  If they only officially
support the SDKs, it could be dangerous to
use >>   undocumented
API's by reverse engineering the php library.
Plus it would >>   be
very time consuming.  >>  Don't
know what the exact considerations are, but
it probably won't be a >>
  big problem. Only the testing
part will be different from other API's, >>
  because we'd have to fake the
SDK responses etc.  >>
 Reply to this email directly or view
it on GitHub.  >>   

----------------------- Original
Message -----------------------
  
From: "Barry vd. Heuvel"
notifications.com
To: thephpleague/omnipay
omnipay.github.com
Date: Tue, 07 Jul 2015 12:22:55
-0700
Subject: Re: [omnipay] Is
anyone working on a Braintree module? (#211)
  
Yeah, but I don't think the HTTP API is
really exposed. They are just offering their
PHP (or other languages) SDK libraries, not
their REST API. See https://www.braintreepayments.com/blog/when-rest-isnt-good-enough/
(didn't find a recent update)
If they only officially support the SDKs,
it could be dangerous to use undocumented
API's by reverse engineering the php library.
Plus it would be very time consuming.
Don't know what the exact considerations
are, but it probably won't be a big problem.
Only the testing part will be different from
other API's, because we'd have to fake the
SDK responses etc.
—Reply
to this email directly or view
it on GitHub.