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
- 3cb75362210a703c43a54f01528655ec760f4d45e79dd131275656d9dbd8151e
- request
- c888c47e95fbba9a16ee73fcd99b3c65311ab32d5abd5d8f4ba73a546809f225
- transaction
- 4123d736846c3279bdf593d8e3179e385135c6639efa57f22be8cce7bb30be9bcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 64526
the chainentry 64526
- sealed to the entry before
- a520cff04065f7209ec08a25248d5e86e7b230252758f693ec9b9cc15c367b0e
- this leaf
- 4010a2ba0218cf4f59c438d811169073d2098388f57504cca018b518540ec6d4
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- TaTPTm30f6vjA5PLvTrjAG+mUuCgShmzRVPoKo5UbCuu/Aesd7kz4aQQrpK0AhvhTBTD5KeaOsQdHU7zldTyAg==