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
- 9c9bb91f7f228ed9b97201845f170bdb665e6881a11edae1b24bd8fc6b2d6097
- request
- f6adda34ed2f9a557cf4cfd3bb5c14f072fa5f455942a8aae800dc327612afca
- transaction
- e6448f8264418e2d70b4ef399ec992d67d20f1014dd06672a236f8355e96b5fccomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 57832
the chainentry 57832
- sealed to the entry before
- 92274f719dc9b1951da3706853e6d10910f376ba9fd31dcd0dcc1f9e012eb7fb
- this leaf
- 0c00b9893f59b84dd2903bb15f46cd94d8b76d0bd3b6d515ba840f59812e1858
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- m/glnnmcsvDlBH/S7uVh109pkOmTIEkmHSKdPik92TEqrRYCfYp8efl39IEUz4CLrsHmTkRdtXTVngt1dn7lDA==