why1 reason
data_leakpayment_card
payment_note carries a payment card number (41************11), which would be written to a permanent public record
what it was decided fromfingerprints
- rule compiled from it
- 69e3692640aa05eb905590b5adbb82f47757e56f383f59a547be335742ffce30
- request
- 3477fce3f34171b7b108467af84fa0b5b1daf958a8c9262b280e142ca12fc74f
- transaction
- d950236ce1d7872b11bafe639b6a68b90952b2bf44e4885c09be161efc847e19computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 36425
the chainentry 36425
- sealed to the entry before
- 098a15103c35940e597cfa2e4d2ecc58ca227355ac97abcd7b2de46486fc1ffa
- this leaf
- 223b2d7597f071ef3b0e04af004ddd2c127042e1a11ae8f590601dec6b15cded
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- DtgGkZM7uqNVJ7z3KJpBCH+URKJMFk3zirJIVmtXK/NnJ4LKDpWBxBeypCPOK+T8DBkLhxkJjwH7MAp/VTFlBQ==