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
- aadab8325d2610d65243fef590969b315c13e74ae9b4f56b3fe4b1e7c94c13d9
- request
- c29bde53f9974978c71a3680e3a0afbbed7c938db5c0e013d460799c518240f3
- transaction
- 729294a01f8ea02b8dc544cabb975510789c17ee609129a22afb26d53f7b3433computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 66605
the chainentry 66605
- sealed to the entry before
- 8ea97e20fc67f378ecb64eba957953e5a95fccc5b0011d7f486718d81b9431ea
- this leaf
- fab92f31028544ab868e4767707ab098087d1b65a7a43fdd637e2210450b46eb
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 7rXYirMk4YkKBVXUQJROycjg4oNV4ydd3uqImM7YTEHaBnW08yJckShjovmRkeifh/67fNfM6Mfbk6CGV/NRDg==