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
- 43feaf91b1c725f120f465ff4a2e6016a8e21a2c94493f93b75d24f2b4e0870b
- request
- 0f569a6ef5aed6eb4fbad855a5ca0a856d2efc166ae558460132215cd2a27cd8
- transaction
- 31caab630623666fcb69d74506a2d4e1b11135b875f6fb99197823c559542bcccomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 18842
the chainentry 18842
- sealed to the entry before
- 91bebd2db1725c93b2059394f587f92cf00d1db3a0795d8562b6842e7318e5de
- this leaf
- 72bba13170cab1827962f741392567072691ce478b43def7ef1d833250e049bb
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- HsWhbnLsKBBhxy17JT9HCiuUO0Mqs4dQXHX7SlJJspw8Fnf71lZQcNm6e8WI5vHWXmtp5QjeTlxk3hMk3ES2Dg==