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
- 82580b38f82a3e1d430cba944b3057cac79f24a886313f749a6a3687d8faaeaa
- request
- 9921e39d8a09235429f4f01654c69149d56bf866ac4fe5f832b30cc29cee16b3
- transaction
- 3c21bf6f03871101469b3dc9eaed252790cb170ec0e4ddd23fbb32a7dec537b7computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 64885
the chainentry 64885
- sealed to the entry before
- 06e01fe82a23f6c4e2712992b8c9230e63f42c5fdf6e1e09b2901be7628fda29
- this leaf
- cf9f5d4e40281dfb456c512b2ccc68bf89275953fa2fe9c194749270e58e913c
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- T83CnEzdnI5M4xdLucNnYNy6Zxe88EDh2BjfSuiS7rpp9k1uLPkhnv4trcGaY1eBdji8HgRtUk6ZR0Kii/FMAw==