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
- a01b6f593538843773406d1ec8ec96ad42af496b3a6e05211ecd51048a92175f
- request
- a0f8968f3b262c2070de59bc4447b4ca86ecea2b174c6df439d10c3dc367025c
- transaction
- 49276abc59deef2d340548d107254241f1a81894a6d5efc1ff067c959bebd152computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 22433
the chainentry 22433
- sealed to the entry before
- 835dfa44d5922f1baeb07a6231eec9d4d0f3ef49f87e2c2f0f6dc2e69adaca82
- this leaf
- d088badfa8ed6a02c909525e826b78d8bf204ac423e7ee183842cfd6cf3831ae
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- QhO0KC2oAy+CSFBR5T9ybr6fPSy+Z85HV43R8thgYW89HpwuDQQMiEoDnEAkS2EDe6KJDroMpZhGXIM6qQzcDA==