This page provides you with all necessary information you need to take your first steps towards testing and integrating BridgerPay's services: check lists, credentials, test data, and more.
Check list
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
Environments
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.
Embed
API
URL
Description
https://cashier-sandbox.bridgerpay.dev/loader
Sandbox environment for "script"
https://cashier.bridgerpay.com/loader
Production environment for "script"
https://cashier-sandbox.bridgerpay.dev
Sandbox environment for "iframe"
https://cashier.bridgerpay.com
Production environment for "iframe"
URL
Description
https://api-sandbox.bridgerpay.dev
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, apm
All the payment methods available by the connected PSP's
Currencies
EUR, USD
All the currencies supported by the connected PSP's
Credentials
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
Test data
As the name suggests, here you will find test entities for checking the main points of our services and methods.
Test cards
Test PSPs
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.