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
- 2b12edf02e4985378d3895b3d7c88332c0fd4b7516b450ba92e7fdaf64b924d3
- request
- 0da2e38dac969e22434a426c0dbd134ac65521965a3552be914b07b216c854f3
- transaction
- 9b322ac80c92050df8600e2976a5b3058e3897e75ca48c0374704ed86a529909computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 44176
the chainentry 44176
- sealed to the entry before
- f82527a9a0394cfa1d5c20a1be3675fb396e65639a8c35bbfe9d7f5f53b09b45
- this leaf
- ae0fbc25c272e28390fcc8ae9a125a60188f8192f4974b50ebd26a95f9ba8f64
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- LVQ1XlExoJ9jNlGFhgQtCuRfL3YBmOuy6wzsbuNBDLP06OkyyiG8QqVAQkk9xKlHtFCC/vSIDcCM2qKtZ7BiCg==