We continue to work hard making improvements to the Braintree Gateway and Client Libraries. Today we released a new version of the Java library. This is a minor release and contains various bug fixes and enhancements. If you would like additional information on what changes were made feel free to check them out.
Change Log: Ruby | Python | PHP | Java | .NET
Summary of Changes
Hope the new release is helpful!
Thanks,
The Braintree Dev Team
Trivia Question: Do you know who issued the first credit card? Click here to find out.
Dear Scott Thompson and John Bodine,
As you may have heard, we recently announced a Credit Card Data Portability initiative. We created it to try and solve a major problem in the industry: vendor lock-in due to stored credit card data being held hostage. Following the recommended guidelines outlined in the initiative, service providers can ensure that any data transfer, whether it's provider-to-merchant or provider-to-provider, is done in a PCI Compliant and secure manner.
Today, both Paypal and Authorize.net offer credit card storage services whereby merchants can remotely store this sensitive information to reduce the scope of PCI Compliance and increase security. As you both know, if one of your merchants ever wants to change to a new provider, your organization will hold that stored credit card data hostage. This is obviously very problematic for merchants.
If your organization chooses not to support Credit Card Data Portability, you could assume a leadership role in proper disclosure. You could determine to act in good faith and disclose to merchants, before they begin doing business with your organization, that they will never be able to get the stored credit card data back under any circumstances.
We work with merchants every day that are in this serious predicament. Just as you've worked extremely hard to build your businesses, so have they. It's unfair and bad business to put others into this situation without foreknowledge.
We hope that both of you will use your influence to do the right thing.
Sincerely,
Bryan Johnson
CEO, Braintree
We've released a new version of the client libraries today. We have been working hard to improve our libraries by adding new features and incorporating all the great feedback we have gotten from all of you. Below are some details around the improvements that we have made. All changes are backwards compatible.
With this feature you can pull back transactions using a variety of criteria such as transaction_id, card type, transaction type, status, amount, etc.
Search Examples Ruby | Python | PHP | Java | .NET
Combo ActionsPreviously when creating a transaction for an existing customer we would use the default credit card stored for that customer. If you wanted to use a new card you would have to create that credit card and store it in the vault as the default card and then submit the transaction. For an existing customer you now have the ability to create a transaction with a new credit card that can be stored in the vault in one call.You can now also update a stored credit card and its billing address at the same time.
Combo Action Examples Ruby | Python | PHP | Java | .NET
Update Credit Card and Billing Address Examples Ruby | Python | PHP | Java | .NET
We will still automatically retry for you on past due subscriptions however you have the ability to manually retry using the client library. Previously this functionality was limited to the Control Panel. You also have the flexibility to specify the amount to be charged if you would like it to be different than the subscription amount.
Manual Retry Examples Ruby | Python | PHP | Java | .NET
Previously you could only refund the full amount of the transaction using the library. Now you can refund a partial amount.
Partial Refund Examples Ruby | Python | PHP | Java | .NET
Hope the new release is helpful!Thanks,
The Braintree Dev Team
© 2010 Braintree Payment Solutions. All rights reserved. Braintree is a registered ISO/MSP of Wells Fargo Bank, N.A., Walnut Creek, CA
