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
- 140d866e5906f51b491a148da8643290fad428ffcc722fdb3283f60a7001ae67
- request
- cfde72bef704ab6eeab0f3ca9d4841c10fe3bd7cbd1ca3f875c397fab0dd0864
- transaction
- e4265db2a27225c4166e34609210a270ea79d0a53a2ab3a4e390d146cca49be5computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 28242
the chainentry 28242
- sealed to the entry before
- 6852d7a7e6d77a0f3f6c4ea3cac83db3805929a3c584ca72a34eef0f0a1f2902
- this leaf
- 5639d6ed17456b3729463c0f711641e3efb83647e8eef5a80d22518cc36e968d
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- d+SfQ+khj0jImf4Ymyo0vXFa+UitDSki3g1QV4sAVTGQD7cXQNe0kpZxrLg6VaYzYHjSF7hcUe2vrbyZxTzLDg==