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
- 5e57edebe7836cfbe96e9bf30e5b5b2c23911c5717c9fdef366cd6d4aca32c70
- request
- 999065d0ae0a1211326ef4a45047ecfcba7f96f741645cd35989bf43c62b6504
- transaction
- e9d3a267062b736c726462f3a602c497a34d33ac667abca03499a55afff3284acomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 63492
the chainentry 63492
- sealed to the entry before
- ce8c6c5986cae13fbb4deb30bfc36ec5072216d5187c15a8a57d55a64cd9e169
- this leaf
- 01abdd3e58c368018dfb9aeea440abbba068bbc6e417cdcdb996e54f889f0520
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- FE//iioJEsVoQD9rW2VpBpy6r5kL2JVGeb/9HKeYA+XJvCMUuU9MD4TS1ZyqOxf1t6OYupjFh8HA+Mk6PtW8AQ==