Before you start, check yourself against the following list to make sure you've requested access to the resources you need and received all the credentials.
Solution: Embed or API
If Embed: regular Cashier or server-side Cashier
Environment: Test (sandbox) or Live (production)
Credentials: username and password for Embed, username and password for API, API key, and Cashier key β you are expected to have a particular set depending on your previous choices; see the table under Credentials later on this page.
Upon successful integration, check the following points.
For Embed: a Cashier widget loads on your side
For API: you are able to get authorized in the BridgerPay system
You receive the "approved" and "declined" notifications in response to successful and unsuccessful payment transactions
We provide test and prod environments for both Embed and API solutions. Although functionality available is the same, the test environments have some resource constraints as you are supposed only to try our services and methods there.
URL | Description |
https://embed-sandbox.bridgerpay.com | Sandbox environment for "script" |
https://embed.bridgerpay.com | Production environment for "script" |
https://cashier-sandbox.bridgerpay.com | Sandbox environment for "iframe" |
https://cashier.bridgerpay.com | Production environment for "iframe" |
URL | Description |
https://api-sandbox.bridgerpay.com | Sandbox environment |
https://api.bridgerpay.com | Production environment |
If, for any reason, you need more resources for testing purposes, we are ready to discuss this individually.
Resource | Sandbox | Production |
Functionality | All available | All available |
PSPs | qube_pay | All agreed and specified in your contract |
Payment methods | credit_card | All that the PSPs available to you provide |
Currencies | EUR, USD | All that the PSPs available to you support |
You will need all or most of the following credentials depending on the services and methods you plan to employ. Note that we provide different credentials for different environments.
Solution \ Credentials | (1) MA credentials | (2) API credentials | (3) API key | (4) Cashier key |
Merchant Admin | + | β | β | β |
Embed: regular Cashier |
| β | β | + |
Embed: server-side Cashier | + | + | + | + |
API: Authorization | β | + | β | β |
API: Cashier initialization | β | + | + | + |
API: Payments | β | + | + | β |
API: Server-side deposits | β | + | + | + |
API: Payouts | β | + | + | β |
API: Refunds | β | + | + | β |
(1) {{user_name}} and {{password}} β Merchant's username and password for Embed to get authorized in the BridgerPay system
(2) {{user_name}} and {{password}} β Merchant's username and password for API to get authorized in the BridgerPay system
(3) {{API_KEY}} β Unique API key to ensure that a merchant's actions and requests for sensitive information are secured
(4) {{CASHIER_KEY}} β Unique cashier key to initialize a merchant when creating a Cashier session
As the name suggests, here you will find test entities for checking the main points of our services and methods.
A list of credit cards you can use for test purposes; any Card holder is valid.
Card number | Expiration | CVV | Simulation |
4012888888881881 | 01/2022 | 111 | Pending until approved or declined manually |
4200000000000000 | 01/2022 | 111 | Approved at once |
Only one PSPβ"qube_pay"βis available in the test environments by default.
PSP | Payment method | Peculiarity |
qube_pay | credit_card | "capture" |