Checkout HUB Dispute Webhook

include the checkout com request payment id value in payment auth details a unique identifier is generated by the checkout com that differs from your orderid this is required to map the dispute back to the original transaction map the checkout com payment id https //www checkout com/docs/payments/manage payments/get payment details (the value that starts with pay ) to the processortransactionid field in your order or order status api request, when you send forter the payment authorization details partial code example "payment" \[ { "billingdetails" {}, "creditcard" { "nameoncard" "jane smith", "bin" "442757", "lastfourdigits" "5149", "expirationmonth" "11", "expirationyear" "2024", "verificationresults" {}, "cardtype" "debit", "countryofissuance" "usa", "paymentprocessordata" { "processorname" "checkout com", "processortransactionid" "pay f2ws3hn4ijquzbytp3v5lsfxge" // unique id assigned by checkout com } } } ] create your checkout com secret key in your checkout com dashboard, click developers > keys and create a key save the public key and secret key credentials to a txt file with the file naming convention "jcbr yoursitename processorname" (e g "jcbr tshirtsexpress checkout") and upload it securely to your s3 folder please notify your forter implementation engineer once you have uploaded these files your forter implementation engineer will securely add your secret key to the forter database and let you know when this step is complete create a new webhook log back into your checkout com dashboard and click developers > webhooks create a new webhook using the following information endpoint url https //api forter secure com/webhooks/checkoutcom/\<your forter site id> using the site id from the credentials section of forter portal https //portal forter com/app/integration/credentials/ authorization header key use the secret key from the credentials section of forter portal https //portal forter com/app/integration/credentials/ signature key copy and paste the checkout secret key you generated in the previous step events select all events related to disputes dispute evidence required dispute expired dispute lost dispute won dispute resolved request for information received entities and processing channels select all relevant channels click create webook test the checkout dispute webhook to simulate a chargeback with the checkout com webhook, please reference checkout com's full list of test cards and scenarios multiple checkout accounts for a single forter site currently, forter only supports 1 checkout account to 1 portal site this means that if you have multiple checkout accounts pointing to a single portal site, you will only be able to set up a dispute webhook for one account remaining accounts will need to provide chargebacks via an alternate method such as the forter dispute api, a csv file, or manual update in the forter portal