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
- a89568c2d62083c8f10cd3811b4a37a00dd40eea7fc968f714ab4f78d36829cb
- request
- 2fec74f9aefc441212a400928c23e4db47c249e673699190d05c6ce25c29fcd1
- transaction
- 57e2a2a6d0b225b8d59735cfec1b57812b1694449dae74557a844bf1d626294dcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 38069
the chainentry 38069
- sealed to the entry before
- fa4d3e6fc9fb739c0f1633ed00f05285a814d441f0f0a24e28d2a3da05d05024
- this leaf
- 6e8694b3dd64b1542419dd17153c38ca6a217c987bbac72069cb02a717c1f977
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- aDCyHgnCFaFbxQ95TGAa6LOBr4SxCxJQZefTXXvcWV7AMg3vZUM5ucvk1zqJRHbyxMEJ+8yNNwI8AdiMSdWrDg==