Checkout NAS Platform 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 (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 log into your checkout com account and go to the "developer" section from your homepage in this section, click on the create keys button to generate unique keys for your webhook you should receive both a public key and a secret key value create a notification click on the notifications tab of your main dashboard under "settings" select the "new notification" option and provide a descriptive name for the webhook in the "name" field (i e "disputes for forter") select events in the events selection, go to the disputes box and click on the "select all disputes" checkbox add your forter and checkout keys in the url field, add your forter 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/ in the authorization header key field, copy and paste your secret key from the credentials section of forter portal https //portal forter com/app/integration/credentials/ in the signature key section copy and paste the checkout secret key you generated in the developer section in step 2 upload your secret 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 https //portal forter com/app/integration/docs/secure file transfer 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 select entities the webhook will send notifications for all of your entities by default, but if you only want to send forter notifications for a specific store/or entity, you can check these in the "entities" section finalize your new webhook click on the create notification button at the bottom of the page to finalize the new dispute notification webhook this will publish your notification webhook and allow forter to receive dynamic dispute updates going forward 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 claims api, a csv file, or manual update in the forter portal