You can always contact support here. The Support Hours are provided at the top of that page.
Yes. We have guidelines, which provide specific details and a complete listing of prohibited products.
Yes. Our platform is set up with reports to help you build and manage your business, whether you need clarity on you conversion rates or insight into your sales and revenue. All of your sales and shopper records are permanent so you can consistently and accurately track them and plan accordingly. Refer to Key reporting & analytics tools.
In June 2018, the U.S. Supreme Court ruled in favor of the state in South Dakota v. Wayfair, Inc. The broad result of this decision is that other states are allowed to tax remote sales. Prior to the ruling, states could only tax sales by businesses that had a physical presence in the state. Now, the economic nexus (economic activity in a state) can result in a sales tax obligation. The economic nexus is based only on sales revenue, transaction volume, or a combination of both.
The impact of the ruling on your business depends on a variety of factors such as the sales revenue, transaction volume, and the state where your sales occur. In addition to the specific state tax laws, the model under which you operate within BlueSnap also has an impact.
Most BlueSnap customers are responsible for collecting taxes themselves. For guidance, please contact a tax specialist. If you are using BlueSnap Merchant of Record (Reseller) model, BlueSnap will be collecting tax on your behalf.
For additional background information, you can refer to this information.
You can view reports, search for orders, issue refunds, and cancel subscriptions.
To use the app, you must have API credentials. And only users with the Reports permission can log on to the app.
Note: Permissions assigned to users of the BlueSnap Console apply when accessing the mobile app. Users who cannot refund an order, modify a subscription, or search for a transaction in the BlueSnap Console cannot perform these activities in the mobile app.
Yes. You can define the statement descriptor in three ways:
- Account level — You must configure an account-level statement descriptor, that serves as the default descriptor for all transactions. Refer to Defining the account-level statement descriptor.
- Per product (only with BuyNow hosted checkout) — If you are using our BuyNow hosted checkout pages, you can set up a separate statement descriptor per product on the Product Information page.
- Per transaction and per subscription — If you are using our Payment API or Extended Payment API, you can also define a descriptor dynamically per transaction and per subscription by including the
soft-descriptorproperty in your request. Refer to the API documentation.
We offer over 100 currencies and 110 payment types. Credit cards, mobile wallets, PayPal, e-Check/ACH, local bank transfer, and SEPA Direct Debit are just a few of the many payment types BlueSnap supports.
With so much innovation, the payments business is growing at a rapid pace. This growth has put pressure on ensuring availability of Bank Identification Numbers (BINs) and a new enhancement was introduced in order to extend BINs to more banks. ISO convened payment industry stakeholders from around the world and after much discussion, they agreed to expand the length of the issuing BIN from six to eight digits, effective April 2022. BINs used to be a four digit number, then became six digit numbers around 5-8 years ago. Now BINs can be 8 digits also.
BlueSnap is currently evaluating and updating all our systems and services to ensure there will be no interruption to your business. We will continue to work flawlessly with the 4-6 digit BINs, and we are testing our systems to make sure there are no issues with eight.
Yes! With a single integration to BlueSnap, you get access to our global network of banks. There's no need to manage multiple integrations, source local acquirers, and comply with ever-changing requirements, as BlueSnap takes care of all this for you. While we can process payments globally in all our supported countries, we can process payments locally in 45+ countries.
Local acquiring increases the number of successful payments and minimizes the costs associated with cross-border fees. In addition, you'll be able to accept more currencies and payment methods around the world, including popular payment methods like PayPal and Apple Pay.
BlueSnap supports local acquiring in 45+ countries. If your shopper is located in one of the following countries, the payment can be processed locally.
- Czech Republic
- Faroe Islands
- India (Sign up for our beta version)
- Israel (coming soon)
- San Marino
- United Kingdom
(Coming Soon) BlueSnap will be taking advantage of the PSD2 requirement for banks to create APIs that allow third parties like BlueSnap to initiate payments directly against a consumer’s bank account. When a customer chooses this new payment type, they will be redirected to their bank’s online portal to complete the transaction.
Yes. To do this, you set up a URL to send a shopper to a specific success page once the shopper completes a purchase. You can then use URL parameters to pull values from the checkout page so you can show them on your success page. For example, you could include the parameters for shopper’s name and email, and these parameters are automatically populated with the actual values from the checkout page. For more information, refer to Redirect after a purchase.
Yes. BlueSnap supports partial captures for card transactions. To have this capability enabled, contact your Implementation Specialist or Merchant Support. For more details on how to perform partial captures, visit the Developer Hub.
Note: A fee is charged for each capture.
You can view many card details using our Retrieve Card Info API Request.
Yes. BlueSnap supports Level 2/3 data in the Payment API. For complete details, refer to the Level 2/3 Data guide in the Developer Hub.
Yes. BlueSnap supports the Payment Request API by securely capturing and tokenizing the shopper's data obtained from the browser, which allows you to process payments using BlueSnap's Payment API while keeping your PCI compliance to a minimum. For complete details, refer to the Payment Request API (W3C) guide in the Developer Hub.
BlueSnap supports the current and previous major releases of Chrome, Firefox, Internet Explorer, and Safari. Support is rolled forward with each new major browser version.
If you decide to leave us, first we would like to know why. We pride ourselves on providing the best product and support in the industry. If we fall short of that commitment, we would like your feedback so we know where we need to improve. You can access and retrieve all data that is not covered by PCI requirements using our Reporting API.
For PCI-covered data (credit card number, expiration date, etc.), we are required to transfer this data to your new provider in a PCI-compliant manner. For more information on this process, refer to Data Migration.
There are many helpful resources available to you. Here are a few of the most helpful:
- Area-specific FAQ pages
- Our documentation: Developer Hub and Support Guides
- Merchant Support
- Your Implementation Specialist
- Stack Overflow: To get started with Stack Overflow, visit their website and create an account. You can search questions and answers until you find what you're looking for. Don't worry if you don't find your answer, you can always ask your own questions.
Updated a day ago