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
- 323b66b7ff8501cb9913eda1d24f51e2aaaabe064d922e91927ce87459edf260
- request
- de9900f8a71d2822c3e434a57e76ba953e867bf1cafba0cf4127cdc6de29b44a
- transaction
- 2e5f4322cd150863a38a85f050b3df156677958c80244b8b459c45f992566bc5computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 25771
the chainentry 25771
- sealed to the entry before
- b9780e0dc4221bbc7591c196987b463491f1cfb932a1a5be41b0b7a62320af88
- this leaf
- 35cb07d24baf93f1d096be56ac493b322413857467c09f3c61f59cef1346eafb
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 0g3459hxFLOTmXdAlH3KuBZJuMp8YY1bYdJDzXzQ9G+Kc4RBh2s41KU970gnoLoylhjZl2F07S2p8pEXVNa8Dg==