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
- 225dc855d4e8ce96e2f1eb6a76495bd8f4396584059d5ddaa8e3e53a9c81a5d8
- request
- c0ab11093bfc64ae0e1384191e1fd37936256431a4141459f1146f3d365694cc
- transaction
- 073b77595f9048e09c45042ccdfa331fe675ee5333db66534b4d60e691278c88computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 17655
the chainentry 17655
- sealed to the entry before
- 280b7b6cc984539c2a9cfb586c2f0671ce23d405d027d67a20afbbe4f3b33dc4
- this leaf
- 4261a328e58a06f139b52846936fb2fad1e4b1950d1b586ea8314750f41b8dd6
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- Vmpdf4dyt56IgneVFYMeAuaXMJLksjb9YAe+WGyhRK7Q89fEHLRKHKXwHCG/sH+M28n4+lwvxW4EIR44fzUhDg==