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
- 6ca6374714a6cafe230599c6d63c4f284f7097111099423370e1781ef8772583
- request
- 67ac895790b9193f80f6436e19b02b6c64ab8be7da9d3dfba47095cd5629f127
- transaction
- c638884ed2d2e523ff204afd00d30337c848473649e75a29107d29830c877abfcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 55918
the chainentry 55918
- sealed to the entry before
- 750f9b2b55de6e84e9ccb3487ad4d8333c1d199367983629c4451161b1d88a3d
- this leaf
- 1c753cb06447af3d1359152ab8d1a61fbe6ac309b6d58404a8fc914dfc175d50
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- XDj7XA7BKLYCkh1KUEiJUu+MJ3ijVMPag2P+ONgp/8SCiJ4RZMRRgnaY0NhNbKyzU5gtaWnWEhrWmVO1RGP/Cw==