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
- b7cfb4e33540e254fde7d8e6fff121e62b36980ae1f63107373d9648232d8a72
- request
- 5a0a97ed3c2255e60c3070590ae0110c0c77e6e71149efab2a0f0e2fa35befe0
- transaction
- 02a1cb8bf40676b22b52a4c8fe7f387d4ca662d7ea006bd0f359b1254362de8ccomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 63203
the chainentry 63203
- sealed to the entry before
- cef4439832fae62b5e3dba2eb1817a1784c0ee7998afb330b980f29bf62f8821
- this leaf
- ef41913bf8f9cec09da2a8f8dbb456773b1141f2d1680671ce83bc2c2be0a3b4
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 7nsG/lnUXTzpdJN2RecA3K31+je7W6zGezPjDeHi8qEmNfNezA4MtcySBmEC49Yck9bkhrWiTXKDmbRcjsulDg==