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
- 9df493ee538c1417e851373c30dc39a68e75107a24292f87456bc0ab738eb2db
- request
- 74f06751a56b020eedbb2f39cf404c0ac4e8adf4362822edf3d28affe1f6fddb
- transaction
- c978846d948b19d4fd36b8517a199f7e55b541d164f9e1dba69a6fe5724f8e5dcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 69215
the chainentry 69215
- sealed to the entry before
- 5df8fcffee24c9c37377f106d9b9bfc25f9f4e68c173d667ad178b99fd45b5f0
- this leaf
- dc30e09a19eeb22f1445d6114fbcceee2550cf4a6fb77997fafd5d562b7c4567
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- +nLZKpJA4wBQXFIUjeWM/Y7IZ/hzTI6blj5Y/gLracWRa54nohoKfcfx8N/MSWh7qfgaIpxzP2CFdxbOCa3lAQ==