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
- d88d60c71711c265600c1a22dbbc3955164102f4825e21aaed5880270e082530
- request
- 8a27ed2ecaf7537b9853773615125b093527a26d2dc753df8998b197e24611e9
- transaction
- ebcce940f0cd5ed271f194b91d3af0e55eb033cd976fae29645018592d78cbb5computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 70845
the chainentry 70845
- sealed to the entry before
- 36bd4b08831ce353cf9a6dba5ce67a4a824d672fc313246c5645d8bdff82b63c
- this leaf
- c7ff7b881b6205b3355648a91af528d7af6caf342b58a9c83225890ca486e550
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- f7nItTWa5F0bMXpZwzQETSXmod5eM9Uq2Pd1grmwx6/9Kp5a70m8GPxIs03Mooi1loQYElJYyTMO7Wrmv16+CA==