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
- d7169a4c86de61c88f41eac05c69148ecdab22af99db71c721c97fd14bbc4a10
- request
- e18c46bdf0e1329d98fa9b66acdcbb7866892e6de9a3edab2314f3142c12644c
- transaction
- 9c39983f76f58bed9de8c8000164d9af26479160208688db5113eefd58990863computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 2670
the chainentry 2670
- sealed to the entry before
- 35eb4288f95cf7c503d0425b7e848bd9490dd0fe5fefdd55fa3e3c11c14ea010
- this leaf
- f3fd10ffca55fe505aabf10c69fffdd564f8ac455e42c6827773d5d974c7e522
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- LICDcO0HUI5FUixBv4piXye+ZDTcFS8nMR0VJCRm06MgBMITibTlz3NfvX8w5Jk4f2CvD145RkOyIN3AybZGDg==