Environments and Assets

All of our sample code utilizes the sandbox environment and asset URLs, these will need to be changed before moving to production.

Below are our shared test credentials for the sandbox environment.

For your own private test credentials and login information to our Dashboard to see your test transactions in real-time, please connect with your Integration Specialist.

Credentials (OID, or organization ID, and authToken) are specific to each merchant’s account.

Most merchants will have one merchant account per location, while some may choose to have separate accounts in order to separate their payment device transactions from their e-commerce transactions.

As a Developer you can create a partner authToken tied to your Gravity Payments partner account that you can submit with each merchant’s unique OID when making API requests. The partner authToken will authorize all requests for merchants associated with that partner account.

Alternatively, you can obtain separate merchant authTokens that are associated with each individual merchant location as described above. Those merchant authTokens can authorize requests for that merchant account only.

Using a partner authToken can facilitate the merchant onboarding process as you will not need to wait for credentials to be generated for each merchant before you can begin submitting transactions on their behalf. Also with merchant specific authTokens, you would be required to store a dedicated authToken in your software application for each merchant, whereas with a partner authToken you need to store only one authToken for authorizing all requests for all of your merchants.

When submitting requests with either partner or merchant authTokens, you will need to include the merchant’s OID as part of your request data, as the OID is used along with your authToken to authorize your requests.