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
- ffa975f2803a5550ea55672c3440e27c5be2f0dcc94e93bb89f33c3c47cd4df5
- request
- 050894caab57d618976d116b620261fac007db392aa17c617c1c1d9771f59dad
- transaction
- b2279ce2aab8ae494ced4e076a7f43912900068a281e5f96ebfefd196c9dc589computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 65769
the chainentry 65769
- sealed to the entry before
- 6ebb1a4d5214b62fe22c0fbd1094b186ddee0da15e190329700d9550c2c27a56
- this leaf
- 2e559a34a6a870d935119b1f96bc95d8407bd66868f29cf8a5c8033227e740b1
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- PNTH8QIVQTxNRXfTzRtM2rw7lqUoZmJJSc19c2RGuFUlS2dMwcVaDcR8ymCfA0XQ/XArKQxRhESuNWefBq8WAA==