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
- c0fcc7d2df465f8cd0934d1b17acd6332f21b3867b38c3c55e685fa0da009eca
- request
- e732d520d439c4f9aae4e202bbaf6eca425c8dec9624f890a440d5becb15b213
- transaction
- 9c0fa7a49be51eef1def58427431a452fa18f3cde75cce0f50578ac22b111419computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 11893
the chainentry 11893
- sealed to the entry before
- b19fd5b4c8d5b5a6f6cc635018257b3564d96333cf6faf14d5f53a6149f3ff23
- this leaf
- 9d4531b05a328b49334f0a3f05eea78fc28c3f9ae01da8d4250c36a4b4a77b88
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- QNbu2CaUjGAoNJWnR/zLS2+LoGvvQbjhwGJZFSZxL9qp2HgHEPqYJsjWUGPrHto/EweMHBYQWELBjuvaLPaVAw==