#EwokTrader

1 messages · Page 1 of 1 (latest)

hollow veldtBOT
radiant cobalt
#

Hi there, how can I help?

midnight stone
#

yeah so i want to create a rule to block request coming from this source

#

is it possible using radar?

radiant cobalt
#

So to confirm, you want to block a payment if it's requested with the above mentioned user_agent ?

midnight stone
#

yeah blocking the request coming from that user agent,, it is spamming this request api
POST /v1/payment_methods

#

having the ip address list in radar block rule does not prevent it

radiant cobalt
midnight stone
#

oh i see,, so user_agent is equal to source here right?

#

let me add it now and see

#

so i have this rule added

#

is it correct? seems that the request api
POST /v1/payment_methods
was still accessible even having the rule added

radiant cobalt
#

POST /v1/payment_methods requests are to create a payment_method, not payments

midnight stone
#

so radar is for the actual payments?
then for that instance, payment_methods, is there any way to prevent api attack on that?

radiant cobalt
#

Can you share with me a PaymentIntent ID so that I can take a look?

midnight stone
#

where can i get it?

is it this one?

ID. req_20FNUO5xgEW3Yc

radiant cobalt
#

Can you show me a PaymentIntent ID that you want to block?

midnight stone
#

okay, so there were no PaymentIntent, there were before, but now only using that specific api /v1/payment_methods

#

another question though, can we change publishable key? any impact?

#

for example, what if pubkey was somewhat hacked, and is using it to attack.
so if i change the publishable key, it will resolve that issue and only will happen again if they got again this pub key right?

but will there be any impact on other data? like recurring payment?

radiant cobalt
#

Please note that the transaction_type for Radar rule is one of charge, payment_intent and setup_intent. payment_method is not one of them.

#

Publishable key, as the name suggest, is meant for public. So it's totally OK for you to reveal the publishable key to any one.

midnight stone
#

oh okay, so could be that they got somehow my secret key

#

thanks, so it won't have any impact on revoking and creating a new secret key right?
and maybe as practice change this often?

radiant cobalt
#

It's entirely up to you. the old key will become invalid once a new key is created.

midnight stone
#

thanks, i think key is compromised and need a new one..

#

thanks for your time and help