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
- 30bd9c751610e5b2d7e27d21aaf9b6fa7829230e69a3870b88a3a1c024f00df6
- request
- 620a42e9c6c7c2a915176a483478345228a9a103c3eeb60bf5894d73801d2fcd
- transaction
- 7239817f63b64012adf619af4cf0a7cf1c5397a89a3b732d8f9e66fa15fa3ae9computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 686
the chainentry 686
- sealed to the entry before
- b0caec8bf6d50da949cff76f8ad6a77c25624273827a78157c4b0a7294f6b5cb
- this leaf
- 8a8011abb4e3cda2aa41dc719b80a2733f10e751a112da0b53d9762d57950e6d
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- m1+C5lazCfWZnW0/YArb1ODojedySuczJiq+gL58tBrgqnVyaOj49UIkiqDVqgMf7hIsiuk4g+RUGl2bRmZtAw==