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
- d212a33cd08ea473bc9a0ed3656b5cef806602b0873bc4ce8610480ad9025d0f
- request
- 9e92a714bc0958ab54cc05ee6210ae308d6d3b166c99d59cf6b9da4c4995a47e
- transaction
- 0c90c108deda8d04736fe460c8b912d254eba9fc053d52b80d6c349bec58a699computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 64953
the chainentry 64953
- sealed to the entry before
- f9e054f53b0ff62ade0fdff9dc61669e82731810c4695cb4e5f671a10e50c42c
- this leaf
- a59e7d6618d15ad7a8288cac9ff48a34677ef461b1d82cefc411d4896aa5fd00
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- C0e427BZ9JtzrkRc2oy2NaOmyHevDxt/oS8V2ebBYUgUY3cDTGNPkgupOBOyyKJviiHQqNdXWB7bA6D37zuIAA==