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
- aab9d3d4202d94187e55d208d12ae72e5eb40ac9da43f6b080fba2e38048b877
- request
- c45290211d8aaa991625146b76465301326261a2949bf768250718001b3df728
- transaction
- e5b5b9c209dc94401805e4607ea58c3c9424f292029ebd77d9ecec2f208ced93computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 73315
the chainentry 73315
- sealed to the entry before
- c40f725b188e01314336a3ebae743051de70fdd7b04fce9b851e1f9a4816118c
- this leaf
- a9e658fe72178656028906e66afb482d2733a27d0cebb1d084b4b9f84c121475
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- b5Ts2XGm6TF47Lu5jG2qrZo/MfOBB2xWJTQ1D2qKIbcbzxBHIIa1sLDJdzpiB9QmczPnfihhvwKl3/UgbdrgBQ==