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
- 53dc9439a337c44b519c1ecb4fe5838426429eb496e6cd7394d417b0e942d822
- request
- c36f9172b2ea14e67d28768776a26597e9e263a77290c66e988948090adf58dc
- transaction
- 98b55b35666e417c096dc9b7825f908edb1d503953ce7e1396ccd8fa082de457computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 73204
the chainentry 73204
- sealed to the entry before
- d25369e5ac071ec017d5c37f7cf922574a1adc969ab71040f7c7c6e03fb34b4a
- this leaf
- c58415b2ac56056b05bf1693eab4c704da3862ed1c624c244961ea1baedfd1e7
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 7riF+82dDf3WF4m6PBGht4geUWkcDRVTsd2h0YMYBInvIEtZddnj7p1ZX3Gy8zfKfJCSBWiO+UgKibBMdgp9BA==