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
- 28a586426ea6e72bb88a1ec5bbe6501a30382ca88995fb9ac0e6c880bae6664c
- request
- 0e5cf949d1e5481400ebf12ea95e223480765be29653b668cebd8fed18a6feb7
- transaction
- 986cddd192142e38738bbc1765cd4587f17a9b74087e6c25cf89a838f85264aacomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 59366
the chainentry 59366
- sealed to the entry before
- e7f3c31c23a72fa091e781ca505b7fd2e372853241aca89d8081dabdf40f1329
- this leaf
- 8d2d729694ff79e3d824e3455ef2a0bd757e11f79f47bf39c27725e74aadffd3
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- HR3HsgMlATimCscfnx1w4RrsGPtQr75ab/04etSFeWDbWSQp3IcRZBJa7GlAsIt4Vua+P83+WE2DUNFPWffoCg==