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
- 505ddb74de25321610ff1e1ea54b5135240f5101e2008b0f03d6afa5eebbf2e1
- request
- fa9d6c3415e4033ede6bc0af1f6b188ab2ab396aebd6378a8c3867412cca38a6
- transaction
- d2b223cc86bf3af554fb0b9f042f8dc90c4cba3086a310c650b4ed044b453823computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 22785
the chainentry 22785
- sealed to the entry before
- ba3e83aaf31bfb44fadbfe7d11ee09da898c490c7418edb61b40cc6f3d5b1b65
- this leaf
- 24e918feecd65239d6a21309d0ad5ccc89377300e8fc8e80fb281bb86c0948b4
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- CHRtVUa8WUnpseeNZYGy8ZRyc2IxX00PSM77AbZjJ7WS1Zb557TOQGL/tjlMnx/0s80wwbx4TlJxkn/MFUKVCQ==