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
- ad65db124843cb18c2a2f18950d95d30a5e6e3559dfb3afdabffe546fa4eb72d
- request
- 06e46892894f579f9254950c2ac5b7ab9b98b9a2735730b2926e9dce5b14171a
- transaction
- 451faf327ae5bdd92c116299e5a61cff2bccd9c1013f5c309679a8185c994ad3computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 64259
the chainentry 64259
- sealed to the entry before
- 0dac346872357ef07543148f60853908e609ec1903936606f88f274ecea0e472
- this leaf
- 54cda7225bdff583041766704618ecaa87e221392060e659b0f326c6603c80b9
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- DdhyeOBL17oOEeTL1f9s5G0D9fKBP3Rhfw3UVzGB1R+6NjMZGU2maEWafnZFa/rzjNQG8crZm1K59T2r5yEcDw==