and more, to get your hands coding immediately.
Our REST-based Payment API can be used to create a modern payment experience supporting cards, API integration with Paypal, subscriptions and more. Make the checkout flow of the best possible experience for your shoppers.
Learn more about the Payment API
Use the Extended Payment API for card processing plus more sophisticated purchase flows using coupons, subscription billing, track purchases based on product, segment, and more!
Learn more about the Extended Payment API
Now you can drop in hosted payment fields into your custom built checkout flow. You control the look and feel through the CSS for a quick easy way to have a custom checkout flow, with the easiest PCI compliance available.
BlueSnap offers a simplified way to take complete ownership over your checkout pages using our API while drastically reducing your PCI compliance scope.
Our hosted checkout pages have mobile optimized options for mobile browser checkout scenarios. Our Payment API can be used for native mobile app development. We offer an Android Mobile SDK to make your native development on Android that much easier.
App selected from mobile store
Payment prompt interface
Coins purchased in packages or via subscription
First time card purchase using Payment Plus API
Hosted Checkout For local language, currency and payment type (Ex. Germany)
Confirmation of payment initiates download
One-click purchase option for returning shoppers
Combine your API solution with our BuyNow Hosted Checkout pages to offer your local shoppers a custom UI design, and offer your international shoppers an path to alternative payments with localized language and currency with our global-ready hosted checkout pages. Our payment system allows you the most flexible integration so you can choose how to serve your shoppers and still get the best conversion possible.
Typically, merchants will provide a relatively generic message such as Card declined or please try again or contact your bank for more information in order to avoid giving a potential fraudster too much information.
The merchant should log the actual error code and description in their system in the event they need to provide it if the shopper calls.
Some merchants may also want to handle certain error codes differently than the processor handles them. For example, a merchant may decide to decline based on a partial AVS (address) mismatch where a processor has authorized the transaction. In this case, the merchant should send a Refund request immediately to BlueSnap which will in turn cancel the authorization.
See the Documentation to learn more about error handling.