The purpose of this article is to help you establish a connection between BridgerPay and your partnered Payment Service Provider. The first step involves locating the credentials outlined below in the PSP’s portal. Next, you simply need to enter these credentials in their respective fields found in the PSP’s configuration tab within the BridgerPay dashboard. Once this process is complete, a connection will be established in order to start processing transactions.
The Credentials you'll need:
Public Key
Secret Key
Processing Channel Id
Merchant Name
URLs:
Test URL- https://api.sandbox.checkout.com
Production URL- https://api.checkout.com/
Back-office Login URL:
Steps to find your credentials:
1. Open the following website and log in
2. Once inside, on the left-hand side, click on “Settings”
3. Again, on the left-hand side, click on “Channels”
4. Here you will find the API Keys
5. Copy the Secret and Public keys and paste them into the Credential 1 and Credential 2 sections
Set up notifications:
From the Dashboard home page, go to Developers, then Webhooks.
Select New webhook.
Give the new webhook a name to make it easier to identify in the future.
Enter the webhook URL: https://api.bridgerpay.com/v2/webhook/checkoutcom/callback
Enter an authorization key. To validate that the webhook is genuine, this will be in the header of every webhook notification we send you.
Enter a signature key. Checkout.com generates a hash-based message authentication code (HMAC) from the webhook notification contents, using the key provided in your workflow's webhook action. The HMAC will be in every notification you receive.
You can configure HTTP headers which will be included in each webhook notification. You can use this feature to configure a key that you want to provide in your webhook notifications' Authorization HTTP header, allowing you to authenticate requests with your server.
Select the events per the list below to receive webhooks for:
Gateway events
Payment Approved
Payment Paid
Payment Returned
Payment Declined
Card Verification Declined
Card Verified
Payment Authorization Incremented
Payment Authorization Increment Declined
Payment Capture Declined
Payment Captured
Payment Refund Declined
Payment Refunded
Payment Voided
Payment Authorized
Payment Pending
Payment Expired
Payment Capture Pending
Payment Refund Pending
Payment Canceled
Payment Authentication Failed
Card Payout Events
Payment Approved
Payment Declined
Session Events
Authentication Approved
Authentication Attempted
Authentication Failed
Authentication Started
Webhooks are set up at a client level, which means you will receive notifications for all entities and processing channels. However, you can filter the updates to specific entities and processing channels.
Select Create webhook to publish your endpoint. It will be live from this point onwards.
If you need more payment providers for your business, use our connections search engine to find and contact them.