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
- de206c0e201d7e1f25aba20b3233291364f5c89de8edaa2bc98e7f19b0cde80f
- request
- 1d19e322ede78ab556b69ad41ff4fee89240b6c6bf78e5a790fa8bf098ccf8c7
- transaction
- b62efa3ee7b9135e9ecb0617f1cb810e8b13a1310d4fb32c50d247c688bccb3ccomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 40240
the chainentry 40240
- sealed to the entry before
- 7a54fdc99a4c971d3501e79585a08d0f1063f18b66839aa1fbd07c6b581520e9
- this leaf
- 53140716eb8d5262ed142f6167f7d787e8f489935f4fe22b0ca9787328d31fb6
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 1VK+QAbSBuMqbvGw98Z4JFkRRsJHjzIoXaK5m1kndtHeAg8Sa0BOt+0Gt7I4GzA3LaN1sVWt6iudw/FYw3eXBw==