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
- 8ec7b89ad79b15fdab704a618ffd74616f1155f4a02d7060c2de2abc36624595
- request
- e61c7fb17ea1d57ea160dacb9394c1d22b1b27108fcffc3687aaaf086b3dea7c
- transaction
- c3201d183fecde304a63e451aa56c47cbba8cab0486c75f28ae0052fb6d7b592computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 16550
the chainentry 16550
- sealed to the entry before
- 090ce9b8b30bf12645b01cd60e3c6edcaba8c97df72efa6f2add44b5d5641460
- this leaf
- 0a3b40e9d3704a69e53d1d730a7604b885f1297794ee9707f94df2d7b5bd888a
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- J6trCXskCQeXJbOTXSzjpBQndOt9TgbHnEKDbuRSfnaUftQKD6ANT4fQEXPkLz2TiZiutrJYiZfQNmJncUc0Dg==