Sandbox: Difference between revisions
Stankovicsa (talk | contribs) |
No edit summary |
||
| Line 3: | Line 3: | ||
=Sandbox server= | =Sandbox server= | ||
Although Barion payments are | Although Barion payments are very easy to integrate, we strongly advise all developers to use our Sandbox server for development and testing before going live. | ||
There are | There are numerous advantages of using the sandbox server for testing: | ||
*Sandbox is available | *Sandbox is always available, you can even start working at night or during weekends. However, keep in mind that except for the Facebook group, [[Support|support]] is only available during working hours. | ||
*Sandbox is totally self-service, no contract or NDA needed to use it | *Sandbox is totally self-service, no contract or NDA needed to use it | ||
*No transaction fees are spent during development and testing | *No transaction fees are spent during development and testing | ||
*The live and the sandbox systems are completely separated, so the same | *The live and the sandbox systems are completely separated, so you can use the same email address in both (careful, do not mix up the enviroments). | ||
=Limitations in functionality= | =Limitations in functionality= | ||
| Line 18: | Line 18: | ||
*Since the sandbox is not using real money, withdrawal to bank accounts is not possible | *Since the sandbox is not using real money, withdrawal to bank accounts is not possible | ||
*Real bank cards do not work, we provide a test card | *Real bank cards do not work, we provide a test card | ||
*Top-up is only possible with test card | *Top-up is only possible with a test card | ||
*The servers are of smaller capacity | *The servers are of smaller capacity | ||
*Simple SSL certificates are used | *Simple SSL certificates are used | ||
| Line 26: | Line 26: | ||
=Registering accounts= | =Registering accounts= | ||
Just as in the live server, a simple online form is needed to register a Barion account. Each merchant needs a Barion account, or Wallet, as we call it. Payments are credited | Just as in the live server, a simple online form is needed to register a Barion account. Each merchant needs a Barion account, or Wallet, as we call it. Payments are credited to this account immediately after payment. | ||
'''Note''': Always double-check your environment before calling support. | |||
https://secure.test.barion.com/Registration | https://secure.test.barion.com/Registration | ||
| Line 34: | Line 35: | ||
=Opening a shop= | =Opening a shop= | ||
Opening a shop in the sandbox is the same as opening one in the live server. The only difference is that the sandbox is wired to automatically approve all changes, while the live server requires a human compliance officer to approve the shop. | Opening a shop in the sandbox is the same as opening one in the live server. The only difference is that the sandbox is wired to automatically approve all changes, while the live server requires a human compliance officer to approve the shop. | ||
''' | '''You still have to <u>send the shop for approval</u> on the shop editing page.''' | ||
Also prepare for questions and some minor paperwork when switching from sandbox to live. | Also, prepare for questions and some minor paperwork when switching from sandbox to live. | ||
=API URL= | =API URL= | ||
The base URL for the Barion API is the same as the live, with the word "test" added. | The base URL for the Barion API is the same as the live one, with the word "test" added. | ||
https://api.test.barion.com | https://api.test.barion.com | ||
=HTTPS and Certificates= | =HTTPS and Certificates= | ||
All communication with the Barion system must be done using TLS v1. | All communication with the Barion system must be done using TLS v1.2 / 1.3 - earlier encryption standards (SSLv3, TLS1.0, etc.) are not allowed. You can test your solution on the Sandbox server. | ||
Our sandbox server is using more economical certificates, than the live server. | Our sandbox server is using more economical certificates, than the live server. A standard HTTPS certificate is used, instead of Extended Validation (EV), and a less well-known brand has been chosen. This does not affect security and development, and applies only to the sandbox. | ||
=Test cards= | =Test cards= | ||
The sandbox server is connected to a card acquirer, so all transactions using the test card reach out to that server. This can cause a variation in card processing time. | The sandbox server is connected to a card acquirer, so all transactions using the test card reach out to that server. This can cause a variation in card processing time. If you make several payments to a merchant, the account can reach a balance where another level of KYC is required, and the account is temporarily suspended. Suspended accounts can initiate payments, but can not send or withdraw money. Drop a mail to support if run into this, or cannot avoid it. | ||
<br>Each test | <br>Each test card is represented with a different value in the response of <code>GetPaymentState</code> (see <code>FundingInformation</code> -> <code>ProcessResult</code>) | ||
[[file:Test-card2.png]] | [[file:Test-card2.png]] | ||
| Line 121: | Line 122: | ||
=Payment GUI= | =Payment GUI= | ||
The payment GUI in the sandbox server is the same as in the live, with | The payment GUI in the sandbox server is the same as in the live environment, with the following exceptions: | ||
*A black bar is present at the top, | *A black bar is present at the top, displaying the "sandbox server" message | ||
*The Comodo Site Authority is missing, since the sandbox server uses a different SSL certificate | *The Comodo Site Authority is missing, since the sandbox server uses a different SSL certificate | ||
*The URL has the word "test" in it | *The URL has the word "test" in it | ||
*It only | *It only accepts test cards, no real cards can be used | ||
*All payments are with "test" money, not real money | *All payments are with "test" money, not real money | ||
| Line 131: | Line 132: | ||
{{NotificationBox|title=IMPORTANT|text=Confirmation | {{NotificationBox|title=IMPORTANT|text=Confirmation emails are actually sent out in the Sandbox environment as well, so DO NOT use any real email address that does not belong to you. Use your own personal or development email address, or if you do not care about the email itself, use the @example.com email domain. | ||
|color=#1993c7}} | |color=#1993c7}} | ||
=Using the Barion Web App in Sandbox mode= | =Using the Barion Web App in Sandbox mode= | ||
You can log into the Barion Web App on the same URL, with the word "test" added. A black bar is shown on top of each screen to help differentiate from the live server. | You can log into the Barion Web App on the same URL, with the word "test" added. A black bar is shown on top of each screen to help differentiate it from the live server. | ||
https://secure.test.barion.com/ | https://secure.test.barion.com/ | ||
| Line 141: | Line 142: | ||
= Using the Barion Mobile App in Sandbox mode = | = Using the Barion Mobile App in Sandbox mode = | ||
You can also use the Barion Mobile App with the sandbox server by entering <tt>test#</tt> before the | You can also use the Barion Mobile App with the sandbox server by entering <tt>test#</tt> before the email address when logging into the app. The title bar of the app turns green to help differentiate it from live accounts. You can download the app from Google Play or from the App Store. | ||
<source lang="html4strict"> | <source lang="html4strict"> | ||
test#[email protected] | test#[email protected] | ||
</source> | </source> | ||
Revision as of 09:30, 8 May 2023
Setting up the Sandbox environment and testing payments
Sandbox server
Although Barion payments are very easy to integrate, we strongly advise all developers to use our Sandbox server for development and testing before going live.
There are numerous advantages of using the sandbox server for testing:
- Sandbox is always available, you can even start working at night or during weekends. However, keep in mind that except for the Facebook group, support is only available during working hours.
- Sandbox is totally self-service, no contract or NDA needed to use it
- No transaction fees are spent during development and testing
- The live and the sandbox systems are completely separated, so you can use the same email address in both (careful, do not mix up the enviroments).
Limitations in functionality
The sandbox server is a copy of the live Barion servers, with some minor differences:
- From the developers perspective, the only difference is the URL
- No real money in the sandbox, all transactions are using "test" money that has no real value
- Since the sandbox is not using real money, withdrawal to bank accounts is not possible
- Real bank cards do not work, we provide a test card
- Top-up is only possible with a test card
- The servers are of smaller capacity
- Simple SSL certificates are used
- Sandbox servers are updated regularly without notice (we are doing our best not to lose any data)
Registering accounts
Just as in the live server, a simple online form is needed to register a Barion account. Each merchant needs a Barion account, or Wallet, as we call it. Payments are credited to this account immediately after payment. Note: Always double-check your environment before calling support.
https://secure.test.barion.com/Registration
This URL is identical to https://test.barion.com/Registration, the word "secure" can be omitted.
Opening a shop
Opening a shop in the sandbox is the same as opening one in the live server. The only difference is that the sandbox is wired to automatically approve all changes, while the live server requires a human compliance officer to approve the shop. You still have to send the shop for approval on the shop editing page. Also, prepare for questions and some minor paperwork when switching from sandbox to live.
API URL
The base URL for the Barion API is the same as the live one, with the word "test" added.
HTTPS and Certificates
All communication with the Barion system must be done using TLS v1.2 / 1.3 - earlier encryption standards (SSLv3, TLS1.0, etc.) are not allowed. You can test your solution on the Sandbox server.
Our sandbox server is using more economical certificates, than the live server. A standard HTTPS certificate is used, instead of Extended Validation (EV), and a less well-known brand has been chosen. This does not affect security and development, and applies only to the sandbox.
Test cards
The sandbox server is connected to a card acquirer, so all transactions using the test card reach out to that server. This can cause a variation in card processing time. If you make several payments to a merchant, the account can reach a balance where another level of KYC is required, and the account is temporarily suspended. Suspended accounts can initiate payments, but can not send or withdraw money. Drop a mail to support if run into this, or cannot avoid it.
Each test card is represented with a different value in the response of GetPaymentState (see FundingInformation -> ProcessResult)
CARD 1 - SUCCEED - the card transaction was successful
- BIN: 4444 8888 8888 5559
- Expiration date: any future date
- CVC: any 3-digit number
GetPaymentState result: Successful
CARD 2 - FAIL - the card transaction was unsuccessful: card number, CVC or/and expiry is wrong.
- BIN: 4444 8888 8888 4446
- Expiration date: any future date
- CVC: any 3-digit number
GetPaymentState result: ProblemWithCard
CARD 3 - FAIL - the card transaction was unsuccessful due to insufficient funds
- BIN: 4444 8888 8888 9999
- Expiration date: any future date
- CVC: any 3-digit number
GetPaymentState result: LowFunds
CARD 4 - FAIL - the credit card has been reported lost or stolen
- BIN: 4444 8888 8888 1111
- Expiration date: any future date
- CVC: any 3-digit number
GetPaymentState result: LostOrStolenCard
CARD 5 - FAIL - the payment card was declined by the acquirer
- BIN: 4444 8888 8888 3331
- Expiration date: any future date
- CVC: any 3-digit number
GetPaymentState result: Declined
CARD 6 - FAIL - Due to potentially fraudulent transaction, the monitoring system declined the transaction
- BIN: 4444 8888 8888 6664
- Expiration date: any future date
- CVC: any 3-digit number
GetPaymentState result: FraudulentTransaction
CARD 7 - FAIL - the card transaction failed due to the card system
- BIN: 4444 8888 8888 7779
- Expiration date: any future date
- CVC: any 3-digit number
GetPaymentState result: CardSystemError
CARD 8 - FAIL - the payment card did not support SCA at the time of the transaction
- BIN: 4444 8888 8888 0006
- Expiration date: any future date
- CVC: any 3-digit number
What is a soft decline?
If you are not sending an exemption the charge will succeed.
GetPaymentState result: ScaSoftDeclined
Payment GUI
The payment GUI in the sandbox server is the same as in the live environment, with the following exceptions:
- A black bar is present at the top, displaying the "sandbox server" message
- The Comodo Site Authority is missing, since the sandbox server uses a different SSL certificate
- The URL has the word "test" in it
- It only accepts test cards, no real cards can be used
- All payments are with "test" money, not real money
Using the Barion Web App in Sandbox mode
You can log into the Barion Web App on the same URL, with the word "test" added. A black bar is shown on top of each screen to help differentiate it from the live server. https://secure.test.barion.com/
This URL is identical to https://test.barion.com/, the word "secure" can be omitted.
Using the Barion Mobile App in Sandbox mode
You can also use the Barion Mobile App with the sandbox server by entering test# before the email address when logging into the app. The title bar of the app turns green to help differentiate it from live accounts. You can download the app from Google Play or from the App Store.
test#[email protected]