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
- 0ca9e9ddfe4dac5fd932737c7b980854bf39205703bc1faa85712de2ed166214
- request
- 42c4da51675caf7717226ee522e540699dd2566bea459c6ff16a49eef4c1f9e3
- transaction
- 2c148ba7d3e1fe07fd4478dda36d57d712810892a7895fbdf8a066102e12351acomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 27889
the chainentry 27889
- sealed to the entry before
- 45af9da9e74efeb7cb53c79f25121eda25385f92be0c0ec8231c3df6b24bca2d
- this leaf
- 5efd97b1c88f7979ead159e1288c59fc0dd196572c057fc1b0d00d7539736d12
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- kaRtL5FW0e4Pcv5V0tHnkEJ5FJQqoCBS4NienS65Z8ya1oaymJO7xZyTSgoQJVFf3ZZuo4EeEwGHgspKc3BTDQ==