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
- 72ff91afa34b2739e0354d488aab9587cdd0b89b335aa4b91c3bd48128432c21
- request
- 7618d004bd94465ddfa939b53f1766a0c9207490d340fddcb21244ea21d2603c
- transaction
- 066c2b24c68b3db7d19d6b469cb852cdc3147a8c67840bc3f283ab909344f156computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 21326
the chainentry 21326
- sealed to the entry before
- 871a0782cbd147fa181ebdba1fcf7f795886f08cafd04feca24c57647220e3a5
- this leaf
- 071ba34b46992eff783f51cfef9fa32800f983732aef193a10fc1ab4c68bc04f
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- aC0Qrm6nsa5ljakFGJFCLQbWaC0ATU5LL7FrlClFNUIz0b+B6jybWgKh/giSNx50IU8NsX0kg5jezZBg+VUSBA==