[
{
"title":"Integration steps",
"link":"https://doc.chargebackhit.com/integrate/integration_steps/",
"text":"Step-by-step instructions for the technical integration of the chargeback system.",
"imgSrc":"https://chargebackhit.com/wp-content/uploads/2022/09/Fraud-prevention-tool-960x320-1.png"
}
,
{
"title":"Products",
"link":"https://doc.chargebackhit.com/products/",
"text":"The guides section for products offers comprehensive information and resources to help merchants understand and effectively use the system to monitor and mitigate chargeback risk.",
"imgSrc":"https://chargebackhit.com/wp-content/uploads/2022/09/Fraud-prevention-tool-960x320-1.png"
}
,
{
"title":"HUB",
"link":"https://doc.chargebackhit.com/hub/",
"text":"Chargebackhit is a centralized platform for administrators to manage and view chargeback alerts.",
"imgSrc":"https://chargebackhit.com/wp-content/uploads/2022/09/Fraud-prevention-tool-960x320-1.png"
}
]
Step-by-step instructions for the technical integration of the chargeback alert system
The
Chargeback
API
conforms to REST design principles, featuring resource-oriented URLs, JSON-encoded request and response bodies, standard HTTP response codes, and authentication protocols.
Steps 1-2 are recommended to be performed by the developer and steps 3-6 by the account holder.
When integrating Chargebackhit, consider the total response time for your requests, which includes network latency, data enrichment from third-party servers, and the matching process to apply your rules and configurations.
SLA response times are under 2 seconds for inquiry, less than 24 hours for init-refund according to rules, and not critical for all other alert types.
Step 1 Login Information
Receive an email invitation with credentials for accessing the web portal
Chargebackhit
HUB
Get API keys (public and secret key) obtained from the
Guide
This page with settings for Chargebackhit users to configure their preferences.
“Settings”
section of the web portal
Step 2 Notification URL
Create and specify a notification URL for both the sandbox and production environments
Notification URLs can be set and modified within the
Guide
This page with settings for Chargebackhit users to configure their preferences.
“Settings”
section of the web portal
Step 3 Signature creation
Generate a digital signature using SHA-512 hash function encoded in base64. This signature uses the concatenation of the public key, JSON-encoded request data, and the public key again as input.
Verify the integrity and authenticity of notifications using the public and secret keys to calculate the signature. Headers of each request are to be placed in the following:
Parameter
Description
Example
signature
Signature of the request allows verifying whether the request is genuine.
MjNiYjVj…ZhYmMxMzNiZDY=
public_key
Unique identification, which will be shared at the moment of registration along with the Private Key.
It is a straightforward process, but in some cases, we need to apply
Guide
Internal logic for quick matching of alert data by the system in real-time.
specific matching
algorithm.