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
- 83a9da252e294d150b1c7272410689f79b488655d4c31cbc415036f84b9e4d08
- request
- 93cc796722df8c887aaf707fdb5d840cb6118ab420f93960dba9ed73cfcd1610
- transaction
- 58b30f736c23bf4d88ac225d43e28383e8859a9d9cc8eff0f2f411e41510ff66computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 481
the chainentry 481
- sealed to the entry before
- a455184608552ca8d4875084031307dd20ee2d0871f4d20b847d04b2302dda97
- this leaf
- bf4d644135469eca7493c7b976670470e43c922b2cb8af61ccc2f0122f43c260
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- QylmUOuunzKRXhrLaROnlRXRLbC1b6dFhB0AE5m/+xLqbGJNCl+uboedKaC/pZvfJJLyR9LiaZ388VoGo9NTCw==