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
- 0490ba572a6cbef470ee342f70aee67a591fe25bb4a3f547a95fcc949cc09dc3
- request
- af58bf5b01a549d1612e55432e49d22a01dea0b697d46b674a21e112c54e767d
- transaction
- 87a59cffb6ab35f0eaca2e82b74bf11d11dede2f7918d32c6815d0fa3533eb9dcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 12141
the chainentry 12141
- sealed to the entry before
- a91614e318a3edc2ebe22ac0cd2355c7cd49eede5583aec522f959301e8bae8b
- this leaf
- 86e6d1f6a71dc3886ba37fbef121944efeba73e959bf6893b396d300a110f9d6
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- wXpZVXnVFn9ajxQ3iMGPN/razCe8KbSQ06Dt7VFfkWtdrmBJylQJvo3aAs/e+s0LSkwAcVuPTZ1iSo9RVoWWAA==