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
- 1e40a77238a469bc18cf130ec733bee22fa62fac3e048103efc4122d41fc3407
- request
- 96e5f6454649cdf5daf224b52cac20b7f5cb7b52bf307a3e2f58c83962cb2043
- transaction
- 2c11f00760826f6c142fe0225a4da49173b0c37e11744bf12196ac2a84439aaacomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 34911
the chainentry 34911
- sealed to the entry before
- 6a02fa8e68e6a188514ec881c2aa5b6456ce2601868cfca12214b865f2a3acae
- this leaf
- 4d6756203e678b25235cb680128e3e325c7dc56d71fd213ee910f97e0598840b
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- RIdcyrOd7AjHq7NuB3roWAOa6rg89SSUuUPszu9Z4KKoHkms8doeX4E55IZrhe1L6Z2QxcmG15nshkZZB5icDg==