Skip to main content
Checkout.com

How to find API Credentials

Maria Garozzo avatar
Written by Maria Garozzo
Updated over a week ago

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

  • Merchant Name

  • Processing Channel Id (optional)*

  • Checkout.com 3D URL (optional)**

*In case this was provided by Checkout.com, you must also enable '3d Secure' and 'Automatic TryNon3d' toggles.

**In case you are enrolled in Checkout.com anti-fraud service, configure the provided URL here and enable the 'Use Fingerprint' toggle.

URLs:

Production URL: https://api.checkout.com/

Back-office Login URL:

Steps to find your credentials:

1. Log in to your Checkout.com back office

2. From the left-hand side, click on Developers

3. Click on the Keys tab and here you can generate or find your Public and Secret Keys

Set up notifications:

  1. From the Developers section, go to the Webhooks tab.

  2. Select New webhook

  3. Give the new webhook a name to make it easier to identify in the future.

  4. Enter an authorization key. To validate that the webhook is genuine, this will be in the header of every webhook notification we send you.

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

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

  7. Select the events per the list below to receive webhooks for:

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

    2. Card Payout Events

      • Payment Approved

      • Payment Declined

    3. Session Events

      • Authentication Approved

      • Authentication Attempted

      • Authentication Failed

      • Authentication Started

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

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


Did this answer your question?