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
- b056cacfc006d62286965c3de082dc4e7a111dae16977ccc9713db0beb557198
- request
- fc3c8d7313154e57ce3c18ac5adb91e6751f3d8b74cf7c8e03956f02452f3d61
- transaction
- 8f531399ed98d4fde942f8c1f70a99904ed74cfac40d3b6801b144697568970acomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 36325
the chainentry 36325
- sealed to the entry before
- a54a1d9e04641265da6e01accccc71bd2135378a377f48b3afe6132c497272f2
- this leaf
- d2624294adf67d36df2e51b7d55b50906ea2692b6ad8ce882f89c07a5b1238a5
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- mdMK6c0dFQm97l/pwTLOXk8D/8vD05LdJFYQ9OE39c4n8c1A/hHZAON56CY0RuTo/GUOo7E8kry61s5xq369Bg==