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
- d1f08f43cdd729f9bb7cd6c231f6be2adf0158784f41e57371536ddd083b650d
- request
- aa2fb4e26652df1c29e633c762f77303bfe892967c018674c66913d55f467a9c
- transaction
- 09bc44a0a29700029a33c76c52e1a299c215dfbac83efd5d6aafbfcb4545314fcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 67403
the chainentry 67403
- sealed to the entry before
- bbb114aebfbc701636c1078de9336f2209884ab21719e5c3ac2f634b32d5e377
- this leaf
- 82cdfe8936692dc3fa21fa848b9f091eacde8cd31adb54eaf3f269abb8e599f5
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- Gyy0d4qUqKZfJMc9DWEtoTFtHj1o2IxrkvRBdIjlzfGFYtw21dpPUjlQCq5U2uj4Osbx16KfAtdJKsJqFVrKDA==