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
- cb7232db53100e48a3cda34b6fe200da24df5c107130a6ec688d6b0cbb01edf4
- request
- 20ee22205f8fcac6ac61eaea2d8580a714679f28fbc60647527b715551292ccf
- transaction
- d47f9c8658e811ab263cb515d3f3b6e864f58fb8a960e56297f97a6c99f37f26computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 27334
the chainentry 27334
- sealed to the entry before
- 8dadaac3758be3c0559cde97f48c19e152e533d5d3db984e4d7c73ad5dad3bff
- this leaf
- 6023826ba4601d9053f7fe26f1078ee7b519c4fbbd6579f1196b0c1356ef09c4
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 8CBDaFfDhexTS/Cbch/O2B3Rxx1NE3Q91sIgCm7MdwXc60hIJXmSvullzHP0JkPUYR+n6kkAjMfrb45agmEPAg==