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
- 9b040cd474bc22176a2672cbea3ff84292dbc72a420a0fabaf3851559c580de2
- request
- 887da7cd25e5eda5cf08746130e71f99bc209b230a6f4a2aafb0676e050a87e1
- transaction
- 4f8f6b3fbcfeca1fd5e5c36a4147da78ac61856abdc5f647609952b71ca51240computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 386
the chainentry 386
- sealed to the entry before
- d9fd3920d99ba3a43e97112aeba65f561b9bb2bcf56899a7d967277c83e5e67b
- this leaf
- 3791f1f501fa90724bc1aaebeddd5d22665cf4d7d0e08a1f6a7b4016b83a02ff
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- ZCCl75pnHRuo8o8cnS9H9ZCEadgjCjetcqb/g+DudyYJSCuJyULX+PfZ1AFfcltFGdQmWLLmzFSCvmfhi4ShCg==