[---

My Checkout.com API Secret Key leaked! What should I do?

What is a Checkout.com API Secret Key and how it is used?

A Checkout.com API Secret Key is a sensitive piece of information that is used to authenticate and authorize API requests made to the Checkout.com payment gateway. It should be securely stored and never shared or exposed to unauthorized parties.

Here are the main use cases for the Checkout.com API Secret Key:

Securely authenticate and authorize API requests to Checkout.com's services.
Ensure the confidentiality and integrity of data exchanged between the developer's application and Checkout.com's servers.
Protect sensitive information such as payment details and transaction data from unauthorized access or tampering.

---]

[---

1. Code snippets to prevent Checkout.com API Secret Key hardcoding using environment variables

Using environment variables for storing sensitive information like API Secret Keys is a secure practice for the following reasons:

Environment variables are stored outside of the codebase, reducing the risk of accidental exposure through version control or code sharing.
Environment variables are not visible in the code itself, making it harder for attackers to discover and exploit them.
Environment variables can be easily managed and rotated without the need to modify the code, enhancing security and compliance practices.
Environment variables can be encrypted or secured using tools provided by the hosting platform, adding an extra layer of protection.

How to secure your secrets using environment variables

---]

[---

2. Code snippet to prevent Checkout.com API Secret Key hardcoding using AWS Secrets Manager

Using AWS Secrets Manager to manage Checkout.com API Secret Keys is a secure way to handle sensitive data. Here are code snippets in five different programming languages that demonstrate how to retrieve the Checkout.com API Secret Key from AWS Secrets Manager.

---]

[---

3. Code snippet to prevent Checkout.com API Secret Key hardcoding using HashiCorp Vault

Using HashiCorp Vault for managing Checkout.com API Secret Keys is a great way to enhance security. Here are code snippets in five different programming languages for securely handling a Checkout.com API Secret Key using HashiCorp Vault.

Remember to replace the VAULT_ADDR and VAULT_TOKEN with your Vault server address and authentication token. The snippets assume that the Checkout.com API Secret Key is stored under the api_key field within Vault. The specifics of the Vault path and field names should be adjusted to match your Vault setup.

---]

[---

4. Code snippet to prevent Checkout.com API Secret Key hardcoding using CyberArk Conjur

Using CyberArk Conjur to manage Checkout.com API Secret Key is a secure way to handle sensitive data. Here are code snippets in five different programming languages that demonstrate how to retrieve the Checkout.com API Secret Key from CyberArk Conjur.

---]

[---

How to generate a Checkout.com API Secret Key?

To generate a Checkout.com API Secret Key, developers can follow these steps:

Log in to the Checkout.com Dashboard.
Go to the Developers section.
Click on API Keys.
Select the option to create a new API key.
Choose the appropriate permissions for the key.
Generate the key and copy it for use in your application.

---]

[---

My Checkout.com API Secret Key leaked, what are the possible reasons?

There are several reasons why a Checkout.com API Secret Key might have been leaked:

Improper storage: If the API Secret Key is stored in a publicly accessible location or in a repository that is not properly secured, it can be easily accessed by unauthorized individuals.
Sharing credentials: Developers may unknowingly share the API Secret Key with others, either through code snippets, documentation, or other means, increasing the risk of it being leaked.
Logging sensitive information: If the API Secret Key is logged in plain text or in logs that are not properly protected, it can be exposed to anyone with access to those logs.
Weak access controls: Inadequate access controls on systems or databases where the API Secret Key is stored can lead to unauthorized access and potential leakage.
Phishing attacks: Social engineering tactics or phishing attacks targeting developers could result in the disclosure of the API Secret Key to malicious actors.

What are the risks of leaking a Checkout.com API Secret Key

When it comes to the Checkout.com API Secret Key, it is crucial for developers to understand the risks associated with leaking this sensitive information. Here are some key points to consider:

Leaking the Checkout.com API Secret Key can lead to unauthorized access to your payment gateway, allowing malicious actors to make fraudulent transactions on your behalf.
Exposing the API Secret Key can compromise the security of your customers' payment information, putting their sensitive data at risk of theft and misuse.
A leaked API Secret Key can result in financial losses, reputational damage, and legal consequences for your organization.
Developers must follow best practices for securely storing and handling API Secret Keys, such as using secure vaults, rotating keys regularly, and restricting access to authorized personnel only.
Regularly monitoring for any unauthorized usage or suspicious activity related to the API Secret Key is essential to detect and respond to potential security breaches promptly.

---]

[---

Checkout.com API Secret Key security best practices

Avoid embedding the secret directly in your code. Instead, use environment variables or secrets managers‍
Secure storage: store the Checkout.com API Secret Key in a secure location, such as a password manager or a secrets management service.
Regular rotation: periodically rotate the API key to minimize the risk of long-term exposure.
Restrict permissions: apply the principle of least privilege by only granting the key the minimum necessary permissions.
Monitor usage: regularly check the usage logs for any unusual activity or unauthorized access attempts.
Implement access controls: limit the number of users who have access to the secret and enforce strong authentication measures.
Use a secrets manager: utilize secret management tools like CyberArk or AWS Secrets Manager for enhanced security.

By adhering to the best practices, you can significantly reduce the risk associated with Checkout.com API Secret Key usage and improve the overall security of your Checkout.com API Secret Key implementations.

Exposing secrets on GitHub: What to do after leaking Credential and API keys

---]

[---

Checkout.com API Secret Key leak remediation: what to do

What to do if you expose a secret: How to stay calm and respond to an incident [cheat sheet included]

How to check if Checkout.com API Secret Key was used by malicious actors

Review Access Logs: Check the access logs of your Checkout.com API Secret Key account for any unauthorized access or unusual activity. Pay particular attention to access from unfamiliar IP addresses (if you haven’t set up a specific allow list) or at odd hours.
Monitor Usage Patterns: Look for anomalies in the usage patterns, such as unexpected spikes in data access or transfer.
Check Active Connections and Operations: Review the list of active connections and recent operations on your database. Unusual or unauthorized operations might indicate malicious use.
Audit API Usage: If possible, audit the usage of your API key through any logging or monitoring services you have integrated with Checkout.com API Secret Key. This can give insights into any unauthorized use of your key.

---]

[---

Steps to revoke the Checkout.com API Secret Key

Generate a new Checkout.com API Secret Key:

Log into your Checkout.com API Secret Key account.
Navigate to the API section and generate a new API key.

Update Services with the new key:

Replace the compromised key with the new key in all your services that use this API key.
Ensure all your applications and services are updated with the new key before deactivating the old one.

Deactivate the old Checkout.com API Secret Key:

Once the new key is in place and everything is functioning correctly, deactivate the old API key.
This can typically be done from the same section where you generated the new key.

Monitor after key rotation:

After deactivating the old key, monitor your systems closely to ensure that all services are running smoothly and that there are no unauthorized access attempts.

---]

[---

How to understand which services will stop working

Inventory of services: keep an inventory of all services and applications that utilize your Checkout.com API Secret Key.
Communication and documentation: Ensure that your team is aware of which services are dependent on the key. Maintain documentation for quick reference.
Testing: before deactivating the old key, test your services with the new key in a staging environment. This helps in identifying any services that might face issues post rotation.
Fallback strategies: Have a fallback or emergency plan in case a critical service fails after the key rotation. This might include temporary measures or quick rollback procedures.

In summary, the remediation process involves identifying potential misuse, carefully rotating the key, and ensuring minimal disruption to services. Being proactive and having a well-documented process can greatly reduce the risks associated with a compromised API key.

---]

[---

What about other secrets?

GitGuardian helps developers keep 350+ types of secrets out of source code. GitGuardian’s automated secrets detection and remediation solution secure every step of the development lifecycle, from code to cloud:

On developer workstations with git hooks (pre-commit and pre-push);
On code sharing platforms like GitHub, GitLab, and Bitbucket;
In CI environments (Circle CI, Travis CI, Jenkins CI, GitHub Actions, and many more);
In Docker images.

---]

payment_intent

nullable object

The PaymentIntent object for errors returned on a request involving a PaymentIntent.

Hide

Show

child attributes

CLIENT LIBRARIES

$ gem install stripe

STRIPE-RUBY

$ pip install stripe

STRIPE-PYTHON

$ composer require stripe/stripe-php

STRIPE-PHP

MAVEN
<dependency>
  <groupId>com.stripe</groupId>
  <artifactId>stripe-java</artifactId>
  <version>24.16.0</version>
</dependency>

GRADLE
compile "com.stripe:stripe-java:24.16.0"

STRIPE-NODE

$ npm install --save stripe

STRIPE-NODE

$ go get github.com/stripe/stripe-go/v76

STRIPE-NODE

$ nuget install Stripe.net

STRIPE-NODE

SHOW

This is placeholder code

Table of Contents

Table of Contents

Table of Contents

Table of Contents

Table of Contents

Table of Contents

Table of Contents

Table of Contents

Table of Contents

Table of Contents

Table of Contents

Table of Contents

Table of Contents

Table of Contents

Table of Contents

Table of Contents

Table of Contents

Table of Contents

Table of Contents

Table of Contents

Table of Contents

Table of Contents

Table of Contents

Table of Contents

Table of Contents

Table of Contents

Table of Contents

Table of Contents

Table of Contents

Table of Contents

Table of Contents

Table of Contents

Table of Contents

Table of Contents

Table of Contents

Table of Contents

Table of Contents

Table of Contents

Table of Contents

Table of Contents

Table of Contents

Table of Contents

Table of Contents

Table of Contents

Table of Contents

Table of Contents

Table of Contents

Table of Contents

Table of Contents

Table of Contents

Table of Contents

Table of Contents

Table of Contents

Table of Contents

Table of Contents

Table of Contents

Table of Contents

Table of Contents

Table of Contents

Table of Contents

Table of Contents

Table of Contents

Table of Contents

Table of Contents

Table of Contents

Table of Contents

Table of Contents

Table of Contents

Table of Contents

Table of Contents

Table of Contents

Table of Contents

Table of Contents

Table of Contents

Table of Contents

Table of Contents

Table of Contents

Table of Contents

Table of Contents

Table of Contents