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
- d5ac4881c700d3808453d3361181a24cfe73fc37612c604170771cfb1cd13d5c
- request
- 14e13fd39cc75200965274a7727a57bbbcec8ac6d825e574dde7626d52776185
- transaction
- 090854d7b3c3b52b13cbeeecf71fcd3b69a8228e4121c2c547c7f560edad80f1computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 29688
the chainentry 29688
- sealed to the entry before
- d750d8562ecead2a0b4add310aa17a7fdd9d6afdd8a84e2d08bd060e35df1837
- this leaf
- dbf3516cd3fbd2b3493591ef339e0f40c8fff1157ed92fbc84a72854e9bf2d9e
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- +U1j6pprY71c2FE1bLbrtJ4Cpy7nhQmtjEpZIT4O3i5FpkHQ/pGWuikWLOCBlxycAuFL1TjVtH8bxQDAWGwkAQ==