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
- 79a31e9bd923e63c4754f577a8f768b74967bd1b4eb232493f69b02b70884bed
- request
- 82590327af19d26c495f8222b4ea2e29640fab4a34957308a44cdb9b563a4604
- transaction
- 7b934243dafe434402a350a88fdce9e7c850c4e66301798f92677807365654a3computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 44088
the chainentry 44088
- sealed to the entry before
- 61b6110bc120eabf743c7772e3d960e86aeff6b5df289ef95b15d15b5c56fb15
- this leaf
- 70ef2b0e2eece1e82b6169725f45d231a0f81e27faa3d6d34faf7d08e67a6fec
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- imzavCp9NaMYtpi749l97JGlV7unLXJxIpd1bDK14YSM2AIRPlSCYsV830q7NCw+ugurzK8oo9E7IVN+4DkkBA==