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
- 42b09ebfeeba12c5bd08efcbfb65ebb2d41de22c686dfc16a00fff8bab448f56
- request
- b63fd4a51fbcf4a5f138eea21e5afba2a7377ee62003f082098042909ec2dcf1
- transaction
- 53d45c11633c5f6067613cb737efa94c286ce14a4d304fd11cc99137f0cf2c5fcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 3755
the chainentry 3755
- sealed to the entry before
- 465a96583ad0555a48794e5b0bab9386ac6abb0e189065a13c6ae9e1979e6193
- this leaf
- a6d29d3234fc988296455a9e14a2e0ef052cd1d19b76db403e732c6193016467
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- ajWihUynkJataH2hQOpkzL0QAkuKyS78mFYcuXeaHDsJmAUcMrBiNPxxUuaUEu7RPwD/64y9q87GWX2Wnd9vBQ==