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
- ad5bf1096c3a588a68a94666434207df2a8afd17f35eeae1bbca3cdbfdc0faa4
- request
- 684a50e980a402bd8397e353391a3601a760d3a4882bf886eeebf44312265879
- transaction
- c61f906a3ad9a4cb42060f39fe7b5ac7b7492d497917abd89162a94f5d877176computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 20909
the chainentry 20909
- sealed to the entry before
- 3a9840ceb8b55b44faad92e55d691c23c22ff2569799cc8c11e66af5e789085b
- this leaf
- 33c753d13f1e956dda9a4f07c04d99fe691e576848eca54509a11a6cbbe6cbb2
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- Ym0hl0oBY3LHxn8CtXe6TDJJpoRpQE2v6meBB30Ws6D3ceRvCmxS5eHsWcPHejG3TdH4gDFXuI6gg3K6bZbSBQ==