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
- af9569f52bd30cf96ed48416569d2754efbcabcd2da63eb87a9122b8e991759b
- request
- f9dff2e231d0fb34a540add8b2b23cf1589f6080a1893086bc31d13b03b7f51d
- transaction
- aa03109ed8982661a482ecb3c1b1c340da17595cf54d1d45de9aac62519e18d8computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 8452
the chainentry 8452
- sealed to the entry before
- 12f6a53cf9b7cca767a7074a2a323111c5d65c49e8ea00e7489050e033999cd1
- this leaf
- 20f19d6ca870b66b77b98d5a674e702e7d15ff24b829b542ad1041c2655c9ce4
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- RrczIQqOX93mrkhDk6w6RaWJgN9nwRol8lvRLBae+bthcPqB7v6h/F9fIpfsUWCV76fB13thxJoiFWVWQ0WeBg==