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
- 0ea1f35d3c264fa52ea4ba03b8e563174191df4571bf9c941790b0423899fb98
- request
- e5dec82b841bf098aa5b6e80e1828b9c0a8bcef0a4d41495a1ef55c3c2d3943c
- transaction
- 06ad6e23499b7bb75d9cb4005a806a1249c780ddd36d299254e65553de91a5f1computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 2910
the chainentry 2910
- sealed to the entry before
- 0247b2cf3c96018e9b1f44c9e1eb3484a7a1704e4ebb3fb2c780d65e7b664bfe
- this leaf
- e740c0ed3233652339c6303c82703088cef83b2f2c569df24a02ed5d6893d449
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- KFw3HP7y/t4qU0eIACqauP7+JlwZMbzCnur+Jk17FjTRH4DhUpwekkJNFdeEHaJxwdgS8hAL+Byz/SvlPrKWCw==