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
- f697524d564eca5567f1fcc76d8f43da68324906809c402b2e69e9565c79a32c
- request
- d9f1403f4b1304846362e5b8791f70c5af61f1ce5701769c47ba549fcd43fc48
- transaction
- b370cb640be3f4eb05a059a62609268c04ca3d2c71652f2f55141872e598c868computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 10971
the chainentry 10971
- sealed to the entry before
- e28f96e73fc7711dd46223e15dcaf105c844443d070b78caa7b5998a582152ea
- this leaf
- 440f6b18cac50d91ac9cc9dc9a50ce27215ea0d6ff66f0dbc7ab09c63f604fd8
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- GRSeXKtEAjXkTXRgucEwnqZ51WpakR55A7s6cTIdfBBlktm9cgLzB02VZphieWbg5WitGdyVO36crZ2dTZNxBw==