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
- ab84a6286f82e24adcef25985211729a5b82cb6c55648e44ef8b77102133b21d
- request
- 99d5f9201776d1edd32dc310b89e089168092729725b11016aeed29d6b6c223a
- transaction
- c23f75735814deb1f68b7c21ccff6a24c60189897a47a018a12f9f540dfc23c4computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 29046
the chainentry 29046
- sealed to the entry before
- 044ca94e41d74bfd4fe06b75e7770b8fa327f62f5a53f2c6da2019658a4c35c8
- this leaf
- cdbd325737da074bc19806daa3c60fc6357f8b0dbde90ced5bbe3626bc920c87
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- zS76Ee8NkWFdiZb78LlNnY9xU47KPAtpL+4T1roJ1uZ3gu3TbPvudwAT63Kfkjns1d3WqvzOblbrSJHyvcaPDw==