The REST API is going global


Today we announced on our PayPal Blog that the REST API is now available globally. In this post I want to cover some new functionality and which features you’ll be able to use in you region.

First of all it is important to know that the our REST API offers 2 different types of payments that need to be defined when creating a payment through our API:

  1. PayPal account-based payments marked as "payment_method": "paypal" in our API
  2. Credit card payments – "payment_method": "credit_card"

The PayPal payments part is our known experience including the redirect to our page that asks the user to enter his username and password and confirm his purchase. This offers a variety of benefits like being able to select different payment methods or choosing another shipping address. Also when processing credit cards we take care of PCI compliance for you.

Direct credit card processing doesn’t involve any redirects at all: You just create a payment (see here for more details) and that’s it. Be sure to read the part about PCI compliance – when processing credit cards directly this needs to be handled by you!


Credit card processing

The credit card processing through PayPal is right now available for the following countries:

  • US
  • Canada
  • UK

In case your country is not listed: We enable to process credit cards in many countries directly through PayPal accounts!

PayPal account based payments

PayPal account based payments ("payment_method": "paypal") are available every where PayPal is accepted.


Please let us know in the comments or via Twitter what you think about the APIs and where we can improve.

14 thoughts on “The REST API is going global

  1. Alex Albino

    Awesome job on the REST API! This stuff is so much easier to work with. A minor gripe however: Any chance we’ll be getting shipping info back from the REST API? (We cant look up address info after checkout, since transaction IDs are not shared between the REST API and the legacy checkout API)

  2. MikeSmithDev

    ETA on recurring payments? Rebuilding/updating my payments interface and the line from the FAQ “Eventually, our REST API library will replace the Classic APIs” makes me want to develop only for the REST API… though some key functionality is missing. Also are there “custom” fields like in the Classic? Where we can store extra data about the item that the user doesn’t see?

Leave a Reply