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
- abde40487a4af241218843e30348a767f8ca70c3178a23e90bd67c57b710ec18
- request
- 5f42d7aecd8fbef77ce26a07b5b58cb4255483c57dc08c7baecc8ad4bfe02010
- transaction
- 2b728238a183ee61ac40549fe54c88b796c0024cbba8db785118d17536465055computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 70513
the chainentry 70513
- sealed to the entry before
- c551b232f2ee6abe8fbd54377f1b5798b70b38e0cc40d610492f914a39bed246
- this leaf
- 503bedfeaffa447299600d2a12f2ece7260537dbbcb35c7fc3438f34e4b2ed1e
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- dBZZA01DsfCj/1uaxsDRugjlT1AquRIwcP+ypa7TQDPCZ3pGl158PGQjaJ5brhRe/oS3jz7sEONnZ2AsvjqJCw==