Cybersource Bot/Cawler Attack ?

CarmosKarran — Fri, 16 Dec 2022 11:27:14 GMT

Just wondering if anybody knew any info on this. It seems like a client got attacked by a bot and sent many $0 authorizations. How could this happen, does that person need to know the API key to make external API calls? Is that person using a session or token? A little mind boggled right now on how they'd be able to do that.

Both developers guides found on

https://developer.cybersource.com/api/developer-guides/dita-payments/CreatingOnlineAuth/CreatingAuthReqGooglePay.html /echat spin

http://apps.cybersource.com/library/documentation/dev_guides/Google_Pay_SO_API/html/wwhelp/wwhimpl/js/html/wwhelp.htm#href=ch_encryptedData.html#1123566 /echat random

Describe the same way to format the data obtained through google pay. They however describe different ways to format the request.

1) Set the encryptedPayment_data field to the value of the
encryptedMessage field that was returned in the Full Wallet 
response.

2) Set the paymentSolution field to 012.

and

2) In the authorization request under the paymentInformation 
object, set the key field under the fluidData object to the 
Base64-encoded value obtained from the Google Pay blob.

3) Under the processingInformation object, set the 
paymentSolution field to 012.

I'm using the I tried the fluidData way since I couldn't find reference of an encryptedPayment field reference in Simple Order API but it's not working.

topic Cybersource Bot/Cawler Attack ? in cybersource APIs

Cybersource Bot/Cawler Attack ?