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
- 094e9f277c3f75b9ce6ac1116e94298bec0cb735b2595d330675bcfbec1b4625
- request
- a38fdecd50738add4589d1bb6ebb878344113a8abadc9d00fbd88932e38acabc
- transaction
- 4f8ff5b50b044e86603b8abd99d5eb712df10f76224552ad944233c34e085f33computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 40827
the chainentry 40827
- sealed to the entry before
- 342096e008d5b774d15af3dadeda3201794ea7f56c04dddb876f46f5b64f4ba2
- this leaf
- 1e3d514b83f01305195b725438ffe11d898784382551b8f8fe84ed0aa90cddf2
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- Adm6tz4RdSbDdLH0K4eCTqRJwPgTOZSsBNEPTkE1UBWrSobs1SQD0cdlFsjJ+0cYfFMOOt2KTJMmP2ogGAqFCQ==