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
- 774e23d5a2395d6f6fabab09962d538778655cff5211ab66106685d3b9f52cf2
- request
- 4e30d399cbb15ae601e8f0e992c74e9c235e1523c2616ce85971dbd19a8201b1
- transaction
- 66bc3a94bc721bad23319e2f79459c61a6e1c0088f94448a185bef9d870bcba6computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 15606
the chainentry 15606
- sealed to the entry before
- a3fb79fe91b8302c76e0ba56f2eba307e341021def8a2af5c8f7f1df736d76f7
- this leaf
- fe7a627846f1aa652e2bbc46b50cf6b51c5665b0ef180676aededb5a6cf41b09
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- cnddN5SakSpFA8X1wHQPY3T0nUa9dFMLBWiNsXTnslaPo3IDLbWzHqDNEf4Mwd3qbJyvdDIYrxFSmgP1MLNaCw==