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
- 725a513a8906c7f37b17fa550ec2af6b81a9bf3adefec14f911074b2282f3ebd
- request
- a50c6bbda3e41820afcf2767dac95237d0f27f130acfffc10bf658cfa91ab094
- transaction
- 7522cec2e002f09eca84c9feb2ce81d221e68ef2e36f75dbd1b7a9382fcd35c6computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 67637
the chainentry 67637
- sealed to the entry before
- 6c8bb6e12b6789299e88ac46a5f0bfcafac382491a1cc0cfb8e688fa08ec1741
- this leaf
- 7d748a81e9a3448cd6f0e64d666fe8ae2f7cb500e0f731c124f334a4d5e533f2
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- pQMPaX+/8LNHJ0hL2JSqtlyLYR39G145xIyIMRoVgEoAXnhAcgPasn9NJh2X9afpGJnDiRVYfZxsuXa6l2QDCw==