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
- 7940491fd4bcce0994e9ed2c1e7d9f0500bea75a408bcdedf6ec860fe44aa53a
- request
- 1f53f421bdc473cca12d415326fa9cc75e40d48aff9867099ee9a50dd2dfae57
- transaction
- 9ceec7427910324fb34db1bb104a7fee1741c72bf23d0814ec29eefd4de909bccomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 52834
the chainentry 52834
- sealed to the entry before
- e126049c42b5cae970e605e31c6ea8518920baa8181d75d929207cbc71e79b6d
- this leaf
- a774c6c8ed9d9a89af5a0daefb59e39257345366b79f01f070a91ebdcfc02f7f
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- woE5vakxpHiO7RR43jkw2OBOc+/HTiU6MsbdhsYRxoakOSu5ErfAC8TS9GMXXfAm1k7BBOb1FAfnmmi3GNhwDg==