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
- 0726a0204ebce25f1399dc7d78144fc00c0df20d1bfc3c7ed0028802f08839be
- request
- 769e7711043f6bc2b90eaf37bbbe21c58130e0c1c8f41725d2ad715aef6a8052
- transaction
- a052c156a2b2b7499da3dc16828979aa81f692a904d868c6f5b01f31f3d19c13computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 3171
the chainentry 3171
- sealed to the entry before
- 429455fa92b9fb49204355dd94842e3834c139d39e1cc2de14f33f87a558dff5
- this leaf
- e122088eeefecef13933a340052db13cae2ddcf46245e77d897100a3f73517ad
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- dVb+K56107gCeBAz4GKtIFKv4SmDt54SEG9QMILAeeKR/LGK0X7ks5oTS3VdY4Yyyah1k27WQW3GJE1jHfQaAg==