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
- a98d5727ce06859846c95fd05713b000c263decb42fcd8dc783cc46ffdcaab45
- request
- 0de7f8f2df1853c634df982c04698fe35c38f42b1360ff167df0e3aaa9a51e87
- transaction
- f6799574a4b2113b2df642cd3aba003d879f2515913f6f71479a0aa39e87df43computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 19415
the chainentry 19415
- sealed to the entry before
- 4aa3f4124fb8db4355895d901d61d931f5a8fd780b8683de901411943921eada
- this leaf
- 1b296c0fef884adc4a61608e67ad95c37b24a47abe28da1f198be31b38a378ea
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- CE817VwZJnN2gcfMcv5eYuSiUkAOnZ6LgSBfr+b7ZnED7/VhcfSli+0jT/SgtylSf9jB25GHgQa8d8yd3vloDg==