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
- fa5c5cd655ca400ba73296000c80f6b7579a7113e09dad41cbc50f871fcf973a
- request
- e3679ca59b753edc2dfbc25fea66d735e0989a26262010527bb08425190e076e
- transaction
- 12bdc83f2471d48309e8b9169a5b7a3ad94737cc22dbc6c0b1f43449f5e5cf38computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 12983
the chainentry 12983
- sealed to the entry before
- fc9bee7f16fffa1867676d98cc2b7dce276602280a703ebec42cff5f814fd94b
- this leaf
- 3df9a3b61f153daece52fd652c1de476f708bfb72d8b8be2069f633461509d4f
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- xbDlQkBUQ2lXw0fKWb2A+Jsz8NOqmCj1DbP/ZC28vltIhBLoL9tuzVYoyKqCdUJ9yq3peKm7yGHvGRCboshzDg==