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
- 309b559f662ff3d67ff07261ad2d9cde4963b4bba262e327bdea649afea89250
- request
- db87341c02ad4d46d12c503ead1ce356df06d1c2eeb3b334765cb6cb6a4ec518
- transaction
- 495c4a86d86114ff26b20778cddf79212d77d2907d90f6d2c75cf7ea5ea29161computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 48680
the chainentry 48680
- sealed to the entry before
- 81e1a86c78e0e2ffa38e04119e5f2c8afdbd89c468459e51a0511cb5c45011dd
- this leaf
- 3a9299cf203051b7d6b391904c663f9912d9f7ba3fa624aead602c5af1f064b2
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- AAa62OrPd+NdAxXLzEnwJVZ1sNL8w88xtfsoDiCjk20lw07ov6Xb/ikaKBYBoJ7kUOAOmbMzbjLopnlqo36QBA==