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
- add7418cab2a5cbbdc3f72aaf4ae57a819cca1229f1965128244a77c6442103d
- request
- 28e6475efdd49fcd19fcb6c392a975d4b110d829302feee362962e14c017d5c2
- transaction
- 50231e2c601b3e2b062c03c12e56ede6407bf494ff35c862eef88342140e97e1computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 36478
the chainentry 36478
- sealed to the entry before
- 83a96d987cc3cbddbd148f5c2ef3b51282cecce5f9bcb01ba81ab0ce43cd687a
- this leaf
- 3845dc641d0224d79849c5a886cec5a4854dbaa3839c42230d6924b7f4960d0e
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- ++SN4xl45hbT8+nqVzG0r9VWoapeGbPVhAQlc4fY89hIWW21lBZYOdfuGM+6BJ+MhNyDrCMtwlY5JexIKj2NDQ==