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
- d4e344e953500fc57a58652b7fd908b2814f00f17dbbcdf20d8a0fc0601dcff4
- request
- 8a0042fb5a56086b73444598a02973f56d77d62e906545feb7768b1a40ce6ce5
- transaction
- 7b4df0feca7bb5176534b5e40f65c387e9466aaf18e2ab7f64cfaa5557c8f776computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 62987
the chainentry 62987
- sealed to the entry before
- 1d2ea74993dad2e838bdc59ba401b2f00e27fb43adc8c4253d437ee84d39c04f
- this leaf
- 98aa7d475d318d0f1129005d027c6a2abefd5070cdb70991dc7e04fe88bba715
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- a5JxA484d/rzK5jKeaiws6d0NKSjSTQz5JBiEhDebZpEX9RcQpMmsBfF2GYBGTflu9//ga6ly4hx3lFv73raDw==