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
- 2c85aa9f0180cff874b7817a9a23e72d4a66de0b0010f5eb6b369652e8ccf251
- request
- ed3c222fc51d3f15c162f774e9dd8cec9a6849118b21e53c999255a241769755
- transaction
- 1d7bc5609c2a57bf985d5c12a6d2f97c3fb1adf5844790c7c421b9749d5df21dcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 336
the chainentry 336
- sealed to the entry before
- 5a4f9025efa051ecbc48f216455c79b14804ecbd8315cb2c0d683cd17cbf5d75
- this leaf
- ac3fdd50b4d7eee3c296f98002a7ca77fe5f9fb4b9bf192828783be9d0a9137e
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- oXmIi6Ek8jEEECvx2OT8m0LAagZcRR///UW21qd4R1Nacj2EwSbMUWl6ISfu5jrDhZ0Wc/yyYz2B84SfkwuSAQ==