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
- d6e1db7e9574bd2191b376c6ee889d06573a702ebd9938744208a012e0dbe11b
- request
- 4260d7a2bc88481800e5fca7346e5fdf791eca1caec3774defa96206f4fd243f
- transaction
- 774f6c721051734efe38e34e439389bf122d93874e3c7e3f34f05336bd564f2fcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 15367
the chainentry 15367
- sealed to the entry before
- 1ed283dabc7d3d4f484e9a7e242401cc4c2ecf6690407867ed72435e7b28e9dc
- this leaf
- a6303530eaa1fd0c6a37d876505edeca4e2ec7d0bcb4834ac7225960499d1611
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 2FFycTzIIa3OPlN8W3m8oVWUJ6dYqrPpLG0AqeZTm/sR//ZZCnAqLdOoh/9GMZVQMEKOnFW+agJmcgLitj9nCw==