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
- cd668ce01e698f1987b3f19dd7be5682d1453455f0abb6d4282fc63fbe344d82
- request
- 826959516ea9a4316af32b89cf18d7c737a2c522f8bc2ddd439c26817326a2c9
- transaction
- 5171d11b105724c0def8cd766e997e3b4c6688f8c6997c69eaffc6c7cac74f94computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 57337
the chainentry 57337
- sealed to the entry before
- a3db50364ad6e2123126d22885f5ad4add9849060c301929be34a4335bbfee76
- this leaf
- d725c60018e2306da015f2786b8ec2cab8556883798acb3e3c681cb81a54536b
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- AbcsXsH9iBx45AZtFunDRrJeNAwSby8jiSDDzwNFqKfp67UPvFuUVUR7QBAkvRKqHlY6sJnV1AKGBPSTThkbCg==