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
- 4060d1aedc5a30e43963819d3f5ca27a30ed027b46daa15079ea69d6b5903bc3
- request
- eb84aac4d144e90070817e875f171aebdfa74a6574975220de9bd8a167997f8a
- transaction
- cc39b761395a11a04d424e4f49fa9f83880fd8049d43a669b52bce0fbab92efbcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 20609
the chainentry 20609
- sealed to the entry before
- 002e7aba4ed91f4ac58a390545722f93e028454f5e4dc3acfcae86be9de99f6a
- this leaf
- 2023de091bbcd230a2d7f86f6466a0606db37031566ab30dd7425ec196dc55fd
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 4uM7xgG1C7cY6s2tt58cfZayiqcsBjqY+4t3TbuxIMhc6z2pjQLPUQPQL/TZ84WQ9g8QBZPFeYXwEP1mYVNQCg==