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
- a8b06f1e902acdfac1b7caba44615f272491e81bd83019b1d4a6ae4c75701f6f
- request
- 2016c9a5c454a301ea2791c8a5445c84346d1a839ce750902746269b932f8a26
- transaction
- fbe7da02f562b6ceab333d35ba3bb9d81832d87ed0353870e16e28f392ba991bcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 62011
the chainentry 62011
- sealed to the entry before
- b085afd6db123ec6db02b9fd4dafaa57fe8de73dc6b1f5de0b64ac86b92f3f55
- this leaf
- e057562ebcea5440e33f81d14e18bb5a99b2734cfc840264e27b60cf6efbc95b
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- +7ExQbgKvTWVpc08j0fLVJg4kDPV261LXGr3N0imJ3m9cLHI8FogQHun9Yb5W9Jg4OUtfIyalwf27CZKdLgJCg==