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
- 6697c8ced3c1c2ba718b035c884fbbb603c6cf434c1956e482b146052e847d6f
- request
- 2c55415a985d7056ef223c59036790ef7e4f320b5af107c006b438422a510774
- transaction
- c64722e102565f566939067bfc3c5308f6ebfda603dbdaf495054a63fe229cb5computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 2200
the chainentry 2200
- sealed to the entry before
- dca0fa13b6205f2a680ffd9759b7e44f46117684d7b0acc1918d6a8e868f3b5e
- this leaf
- 81fb6990f4dc40596568cca88430fb9a5782acf81c700c90049eba0cfc3a17c0
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- nGe1L0wNFffSyI8qM5B6NII8ah2ZPEoVOEEb4NbbimrkYcOhzH6y8mdKMK/Cle/i5A4aSjtXZUX9JR4/alsgDw==