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
- b9ae0bab74ae025ceb5144548e6f6a526ab1124d883cccfb255b16ca014da4d8
- request
- 9dab5576c1cbe08fec077598ae4166ec3af8594d3538f56e4b3e5de3e87d7a68
- transaction
- f0ef22c661534496bae9a7b453add51893ab47fc3fce1b0d98ede6df5fd52fffcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 30310
the chainentry 30310
- sealed to the entry before
- 3fe05886e1a6b5d9598aedc30339af6070ce2bfd79caab87f5a8b68ef539f423
- this leaf
- 84a4c7bd4764812643ed6dc57a25ed3e4ab43d87c6bc6c7570cf08e684062444
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- DkwLVq1k8zzAQZJnMDQKytRRWLDGkxl0zEYmPipMY/gpqHsiukYYrTx3dag4ago15wEjhTjS1y452R9mZYRlAw==