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
- da311cfd02fbb180b5cb3f42d00f987ec05ce06a69e3d7edbcdf28b45707144c
- request
- ce89279d80ef58ec37453e67c92c378269a0fadceddc03ff97d9fb36efde5786
- transaction
- 4bae4e61b93dd45c695c7f1fb0f612bf416af7e8f677fede4af69db4e199faaacomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 6978
the chainentry 6978
- sealed to the entry before
- b2f7c7e0d9bd7523c40e4270fafcdbc054a1d67aad23aff72a17c792ea6b18aa
- this leaf
- a928b00b40c242d14f957c7a0a5dd866ec5933146c15785e268678bfdb8cb0a3
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- hQVBQo19uBH+m8Ep30uvyh0v0b6be6NAPa7WmLo8/KW9ybjm5eJ3E8ZdQ+/83gE0LUEx4E0mLrXsqnK1HJ6ECg==