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
- c7973429695ddab86127a432843a3947dbca790f594f6bd7dc532eff241c028d
- request
- 93c44045746083aaa02f0cfa1de59b3583e4020eb2eb9c5967f0d4276cd7529a
- transaction
- a51245cb761b9655f871054d1a76ba4ce69f6dfec2fcf2a33fa9365ee193e3b0computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 311
the chainentry 311
- sealed to the entry before
- 53498c463f5bc9cda7dd7252665350bbc3670a13a42314cc493554ab02c5a8fc
- this leaf
- a180301d724b0f8f2a87cf02937eea20b8b3d30c38aeb832b7e6cfeabd2d436f
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- DBWVBDOKsG5eOxlf5BrDMA9/cr4K2+cSp+WkaIAoMD3kBKYhv4TDsge+uiSppxiEOZ93Dbhb3ymkJ0PwlCuZBg==