Getting started

From Barion Documentation
Revision as of 14:02, 6 February 2017 by Birot (talk | contribs) (Time needed)
Jump to navigation Jump to search

Getting started - overview of Barion payments

Multiple payments, feature overview

Possible combinations

Recurring with all

Escrow for 3rd party

Time needed

Working with the Barion API is a no-brainer. The time required to integrate Barion can be as low as a few hours. Of course, the exact time required depends on your needs, your business expectations and several outside factors (system architecture, business process management and available resources). Most of the time, basic integration and testing are accomplished in a couple of days.

IMPORTANT
Don't skip reading the entire documentation, you can save a lot of time for both you and us. We'd rather spend the time developing new features. :-)

Guest and Wallet payment, need for registration

Accounts-fundingsources-withdraw.png

Sandbox and live

Barion maintains a clone of the live Barion secure Server as a sandbox or test server, where developers can experiment with their solutions. The sandbox works with "test" money instead of real, so there is no risk playing around. Sandbox is open, all you need is to register and start playing. Don't forget to read the documentation though. For more information on differences in the live and sandbox servers, read Setting up the Sandbox environment and testing payments.

Skills and tools required

All you need is an intermediate level of web back-end development with the ability and tools to call a REST API. Although there are no specific competency or tool requirements, an up-to-date development environment and toolbox is essential. We balance compatibility and security when picking which latest technology to use. For more information read Calling the Barion API.

Supported currencies

  • HUF (Hungarian Forint)
  • EUR (Euro)
  • USD (U.S. Dollar)

To use the Barion Smart Gateway and the Barion API in a given currency, you must have an active account with that currency.

SSL

Barion servers use https:// protocol to communicate. We advice to use a REST library that can verify the identity of our server when calling the Barion API. Always use TLS1.2, as our support for earlier versions will be discontinued in 2017.

For more information on differences in SSL certificates on the live and sandbox servers, read Setting up the Sandbox environment and testing payments.

PCI DSS certification

Barion is PCI DSS certified. Since you, as a merchant do not handle cardholder data, PCI DSS certification for merchants using Barion payment is not mandatory. The Payment Card Industry Data Security Standard (PCI DSS) is an information security standard for organizations that handle branded credit cards. If you handle credit cards, even if temporarily, PCI DSS certification is mandatory.

For more information read Legal and accounting information.

Going live

When your payment solution is working properly in the sandbox, you are ready to go live. Using the live server requires a real contract and an approved shop, so prepare in advance. Read the Going live guide thoroughly and follow the instructions before going live.

Requirement for Smart Package

Please follow the Barion Logo Guidelines and place the appropriate logo on your page. Our experience shows that it is important for customers to show they can pay with Barion on your web site. We also think than keeping the logo consistent across all Barion merchants helps the entire Barion community. Using the logo is a requirement for all Barion price packages, omitting it results in rejecting live shops.

If you choose the Clever, Smart or Genius price package, you have to provide us with detailed cart content. Use the Item structure within the Items[] property of the PaymentTransaction structure of the Transactions property of the /Payment/Start API endpoint to pass data. The customers will see the cart content during payment and later in their Barion wallet history.

When providing cart content, please follow the guidelines below:

  • Use real product names, generics such as "product" or "drink" will not work. Follow these examples:
    • Canon IXUS 110 Compact Digital Camera
    • Heineken lager 5L party barrel
  • Provide all items in one collection
  • Use all fields of the Item structure
  • You may add discounts as a separate item, subtotals are not checked, so you can use negative prices
  • You may add packaging or shipping cost as a separate item
  • Provide a link to the image of the product if available, we will use it later for enhancing the payment UX

Limitations

Currently we do not allow placing the payment GUI in an <iframe> or similar solution, due to security reasons.