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
- fcd7cf80a368b08128d29dfa23ae722e3e39c8c22c5da5d315db598922ad4da2
- request
- 675341adb75448b2a4bfcde2be6744bbb671c24ac85fb42139cccccbe2a5c537
- transaction
- bfc06a961096788cdd5cf9d3e7d6a2827ec986a6d40dae688766b4df289f8210computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 74185
the chainentry 74185
- sealed to the entry before
- 7cac089a70fb90e2b486512aa49e4d9bf003ffce863442d21addc5a6fabb4e8e
- this leaf
- f465c5787bcb570e73f45063480244038942f5c0f365b7d7f0f36b4fe0cbed4c
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- AMHQ29ADGpFYP70WrgZVyZg+6UArOdTu9ZOQ52PqxrAMuk3Ehs49lb2JUQLT9RMZ5oeDzT1R6Y3AIhexg9iSCA==