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
- 3eb5834d57437bac72ed94063b0d4c036892e297d23de09ae1e1f759f95b0199
- request
- e1ef842bc70b0f1ee2fc548a359df9089e66eeb516a811cd983094259e81c20e
- transaction
- 050327282d791860ac305fa4cffebf60e6d63217730dfbc701d34832d9973929computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 41174
the chainentry 41174
- sealed to the entry before
- 9f790c075d16ba869f835c78aa8958eb06ad592d99bdb28acbbe3eca75cb0acc
- this leaf
- 22afcbe614529622c9d5fe188946ed3d0860effc4f0a37a0e944f97125c3fd25
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 1cCwWLFdbXxdZySpI/QcZokkPdQrofqduO4sZlddag8YkJwi/Py/Q1yl9LVD0zHFFDq9H75FaOBmY8W6+qDRCA==