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
- cfcbd0cedeaf128d031bbc24a0707bc423035d0e1f0616e831e6825e5ef1320f
- request
- 4d4490cf2c7cc35661f44f12b31cd11ba82ee1c2e762d3d53886676140e93b3f
- transaction
- 09f0028eba3759994e7433129efbc7e800c4b8411fcbcb37e59aeaf4d2b2fbe3computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 8077
the chainentry 8077
- sealed to the entry before
- 7b21c8150bb6ed4f929a2a3af883ec7127e3a3fdb0f91a4a895f7bbc65cbad92
- this leaf
- cb1d82d57f9cdc3de72778a9fbd0def95b0d27679dcd5d3aaba0645ab3c606d2
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- DccvBYYuP7UARtxSTZbFZzR7ahksbmUO9hn/FebZMYprd4WpWtfKNMFAFjMP24Mad+sbpC2lE/umy3W/AZnmDg==