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
- d1a7e3fe5275e5c29d2bd9c9f819d2c9b3c06bfdec7375d849f45cefe60061ea
- request
- d2d38e785290ea3b736fd14a0c80c74a39f0cf2e8f9589c42df0ad46e199b7ab
- transaction
- b2d7a362cfd5af02ece93a750ae337f976b66da448b27497221453697f19a060computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 60837
the chainentry 60837
- sealed to the entry before
- c54122205d1f84b2add00ac58ebcc4d5377b814d80fcc7e5708b1557f300b44a
- this leaf
- 505a0608270297e1026b86a1ff13b335ee8163c344dd65944b78e645fbd4b94b
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- zi1DmObb1vSaTNMwAsJQFHkkrmWGUtpjcbPIZXuM+mZSXaTMhjoVy0RUCy+mTuTCvyGY8p357Y5ulSIawnPzDQ==