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
- 29fb36f6a33b270ad8e1f736845562f6f94ec67645313f4a5b7dfd6c44d267bc
- request
- 3e99ec5bc46cc24e74c68cac74da34cf232372fa4f3e531aebc6668de88eeda3
- transaction
- 5b852d31d37108212ec403aed4e8594a1aaf4e5fc2e0dcd9edcc81c44cde10b0computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 27860
the chainentry 27860
- sealed to the entry before
- bfa4a44391832b858cb126a1263d5fe26042340f65ed4d9fe9740f6d5c9d92c9
- this leaf
- 3fab4733778827f6cab61f8513542fc48eaeb1b41fe11983fc921f7b21277c1a
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 6SyqCOESNuexfK/nhr6UiahEw+GlaeB0blm9auegmJAn0DsHaN7zu/x+rLQGaBcielalUAs+FR2tjzwXYGzbAg==