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.

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.

(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.