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
- c6d3778225e95fb64c5732ae95cbe38e3c19e397a56406ecae39648a53864bf6
- request
- b36e3d2652a716754ee76a19a43234a92bd4108a792ce110b1e88e23f25752ae
- transaction
- 9abb008d046ce7be8974258dcdea73371b2280e4d895543220658e0060196ec0computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 48654
the chainentry 48654
- sealed to the entry before
- e13ad5721863f75d4cf271f191a6e91dfa9a558f61e26c1e14de0c534ec86bec
- this leaf
- cd5cd83d8a81d21c0a36d132fbe932ef7c60ced728fc398ce4566269083161eb
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- O/ggONOOhn/gOAxNogPH1DyLvK2aDqkYqaDGdFOXzK0lI+BrSHbt9cAM4Mc5j/cVoisk8ZZyIVw/Z3Mq7uE3DQ==