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
- 85c476ce9fd5ddfe8cfaceab3c784cc6c5c189030f76e6cbec30f5f718b08117
- request
- de5d0c9cf6e06096922125595d4c8640971fa3384cdc6926fb42a3f8cbed14ee
- transaction
- 2ace8637ae86601c24a3ebbb167361edc0ca2677dd1e0f5e59b88a422f31940acomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 50756
the chainentry 50756
- sealed to the entry before
- 979a3c2a50b2f16978749c1481e85ce520f876a1081ca3738a0370b96a8839be
- this leaf
- f520d52808d6260d0f160c11d78c5b2fc80524e4ed4cc6b1af07d2da79947068
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- LH1RWOKY/MuB52KVqOIGeGYQ3bDpWZx/qnUIn0z4D5mbKIQkRPnmBxt6bTDh2Vj50AQKvMY3dxvkalTECZ3nAw==