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
- ae78ca157f7418f5ebfd1166bef0d63bdcb3953626947d360ebde7f7172e43eb
- request
- a47026de1147f56b6385e92f15885ecd7f86a384cbdc33ba7c8dd2a8399ffdb1
- transaction
- 69f487fe5731a165dc596a9f15550036c26f2965867e7c98b43d05be960f37fccomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 54055
the chainentry 54055
- sealed to the entry before
- 09ae5ce3997d28c8b92f0bb19d0f09d99c5442e133a6565cf01df250222f8e41
- this leaf
- 5ea4c35b7f28514cf55094363e4d225edfab6a337e825df3e5bb6665f28a7426
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- +Ia7pvNBBnwe/vVOVh29x7G9mOvruVSsr2Km7lzzQtmvN67DR7hRcgik3ztxSl6K8G2N64Sh2V6Vdb1QJZn/Dg==