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
- 1fe8c58943c75a343789d15c4f0ec16c326bdd701aef36c94633f2a86ae08cc7
- request
- b5d9907e046b875012d7546d8d51800988832261840945d1bd1cee4522ca0494
- transaction
- cc6eb35aea142b5b77dee297afa181818aead0905043407affbbcdca390a8305computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 11905
the chainentry 11905
- sealed to the entry before
- f6b7865bc579f53564b874de190cefef5b7f6f374197061241a45e00f9a9b3cd
- this leaf
- fa2ec380bb4f9785fe00b7a5988c12fcf6518dfc35d03577c475d5863425027b
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 5xxchceolRLRNs6mb75gaD9jnm6h/i2xGy3zVDfLqb21lmHKxxxd9TxkcVzFsoSCcQtWDzMra/KJPzKBB8RMCg==