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
- 35854871ef1325196e3662885dfce569cca2a701432e7507ddf18613a9bba761
- request
- 48abb5930e81f183ba261a1327d29c2a18bd7cafaf193ce889f7f0ab50869905
- transaction
- 1ab06904b4557375160f08fc3b1a54a4b51b3250fd0c36f87d5de8512f2b6f56computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 2630
the chainentry 2630
- sealed to the entry before
- a0904888f6fec6782e9b571f5fae2d74e4f07dc2bcbbe6a6817f78b93a34a421
- this leaf
- 5b2ea8b4086efdfbd66ce737762120b249df319415498dbaa8fae7eb2b84875f
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- IGXX191l1ZaINxTnMvQ3xztZ5Zyq9VR/RQyGvlEZx1CExIBiZikECzkwemswmSdFJPoNWiHW9tsu5sTkoN7EBg==