Getting started: Difference between revisions
No edit summary |
|||
| Line 5: | Line 5: | ||
|} | |} | ||
=Multiple payments, feature overview= | ==Multiple payments, feature overview== | ||
=Possible combinations= | ==Possible combinations== | ||
=Recurring with all= | ==Recurring with all== | ||
=Escrow for 3rd party= | ==Escrow for 3rd party== | ||
=Time needed= | ==Time needed== | ||
=Guest and Wallet payment, need for registration= | ==Guest and Wallet payment, need for registration== | ||
[[file:Accounts-fundingsources-withdraw.png|800px]] | [[file:Accounts-fundingsources-withdraw.png|800px]] | ||
=Prerequisites= | ==Prerequisites== | ||
=Sandbox and live= | ==Sandbox and live== | ||
[[File:Live-sandbox.png|600px]] | [[File:Live-sandbox.png|600px]] | ||
=Skills and tools required= | ==Skills and tools required== | ||
==Supported currencies== | ==Supported currencies== | ||
* HUF (Hungarian Forint) | * HUF (Hungarian Forint) | ||
| Line 27: | Line 27: | ||
To use the Barion Smart Gateway and the Barion API in a given currency, you must have an active account with that currency. | To use the Barion Smart Gateway and the Barion API in a given currency, you must have an active account with that currency. | ||
=SSL= | ==SSL== | ||
=PCI DSS certification= | ==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. | 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_accounting|Legal and accounting information]]. | For more information read [[Legal_accounting|Legal and accounting information]]. | ||
=Going live= | ==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|Going live]] guide thoroughly and follow the instructions before 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|Going live]] guide thoroughly and follow the instructions before going live. | ||
=Requirement for Smart Package= | ==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. | 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. | ||
| Line 51: | Line 51: | ||
*Provide a link to the image of the product if available, we will use it later for enhancing the payment UX | *Provide a link to the image of the product if available, we will use it later for enhancing the payment UX | ||
=Limitations= | ==Limitations== | ||
Currently we do not allow placing the payment GUI in an <code><iframe></code> or similar solution. | Currently we do not allow placing the payment GUI in an <code><iframe></code> or similar solution. | ||
Revision as of 11:13, 6 February 2017
Getting started - overview of Barion payments
Multiple payments, feature overview
Possible combinations
Recurring with all
Escrow for 3rd party
Time needed
Guest and Wallet payment, need for registration
Prerequisites
Sandbox and live
Skills and tools required
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
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.