We announced a Credit Card Data Portability initiative earlier this year to address a serious problem of merchants unexpectedly having stored credit card data held hostage by payment providers.
We also wrote an Open Letter to the CEO’s of Paypal and Authorize.net inviting them to either embrace Portability or do the right thing and start properly disclosing their policies.
Our effort recently got a big boost when DataPortability.org, the largest and most well known data portability group which has received support from major web firms such as Google, Facebook, Yahoo! and Microsoft, recently validated the initiative by accepting Credit Card Data Portability as an active working group. This is the first business-to-business portability effort from the Data Portability group.
We’ve been satisfied to see that an increasing number of merchants are now making decisions about who to use for payment processing in part based upon whether or not they can get stored credit card back. Payment processors are now starting to feel the heat as more web developers and online merchants are aware of their business practices.
We always figured that adoption by other payment providers would be slow and primarily driven by losing new business and existing customer discontent. To our pleasant surprise, we’ve been encouraged to see several forward thinking providers follow suit sooner than expected.
To date, DataPortability has dealt primarily with consumer facing data portability issues. Credit Card Data Portability is the first business-to-business related effort.
They’re trying to make data portability policies mainstream for all businesses, just as privacy policies are today.
Join us in our efforts to make credit card data portability the rule instead of the exception.
Comments: 1 | Post a CommentThe Braintree badge is now available to our customers. Using this badge will help you communicate your commitment to credit card data security. Select from two different styles and colors. Get yours today!
World Cup coming to an end got you down? No worries; we have good news to cheer you up! We continue our hard work to improve the gateway and client libraries. We want to make sure we’re continually making improvements to the gateway and delivering those improvements to you as quickly as possible. That is why you will continue to see frequent releases from us. So don’t fear -- unlike the World Cup, you won’t have to wait 4 years before our next release. See below for the new things we have done to enhance your experience with us. As always, we want to hear your feedback, so keep it coming.
There are a few reasons why an API call might return an error response, and it varies depending on the API action. For example, when creating transactions, you’ll get an error response if any parameters are invalid, or if the transaction is declined by the processor or rejected according to your processing rules. Checking for several different outcomes is inconvenient, so we’ve added a single error message to error result objects.
Error Results Docs: Ruby | PHP | Python | Java | .NET
In addition to being able to specify a country by using its name, you can now specify the country for addresses using alpha2 (“US”), alpha3 (“USA”), or numeric codes.
Countries:
Ruby |
PHP |
Python |
Java |
.NET
Specifying country:
Ruby |
PHP |
Python |
Java |
.NET
We’ve supported the ability to search for expired credit cards in the control panel, and have now added it to the API as well.
Docs: Ruby | Python | PHP | Java | .NET
We now provide the gateway rejection reason on transactions, indicating whether a transaction was rejected because of AVS, CVV, or Duplicate Transaction rules.
Docs: 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
