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
- 896ceece24aec74e3fd6a4674da603ec1630d06dcb1ff6880b3eddf1e190fe6f
- request
- d90fabc8346ca25118b332cc49c8fe8525d142a1fd5d68bfa6d88189a1a8af57
- transaction
- fe0de8fef72bd29eb1fe480b0fe5f545c90a206207e969d5bdff1056bc7a9a80computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 39673
the chainentry 39673
- sealed to the entry before
- d47608d0c0c01d9c485c65edf21cef0bc38a1e18919656d66e5ce2dd3361c01c
- this leaf
- 1f8d508cc727ecd1898d5545dbaa238349fcbf026f69ec0095eec8a246b53aac
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- CsMxh/XQimk9bo/1PFmAzMRAxcOtyyjwA/QAEzxPIvRGmQ625h2cgTHXNHeVVFlTU7xQy3pKMkdKR3FsaDcTDw==