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
- 99f2db53194119463efcaaeec0ef038163744852695e351c77b77e8f7b673f93
- request
- 90aca6081c4f48e9957f2eaa8b96e4cddb410fa8d23872ef199ac22cd7580911
- transaction
- ed559ef16047d74b9a7bc9212e0ab7f1b8a4b17910b6fcd6a98aa7162fd35007computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 16226
the chainentry 16226
- sealed to the entry before
- 0d78b8cc6f31dff00cd1001bd68225abd5f1f495233bf871bbc60378a32c3506
- this leaf
- 37d7a2896e9b0d1d264e7d6ef07071777c6b4652f675ed963c8d2ad80bde4e50
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- IFxdtEPB9zTcwA66WN7NveXodD6daWIGLcYGI8s3NVs4vSPmj0l4C3z3Vs9SLyOIwEpfZVpz0SNZOX7nNHobAg==