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
- d154f1b66c5e3571fbb7e55525a24539dfd02e119f39378407d9760f7ffe3ddd
- request
- 7b041fa1e6ef1ccdda01a05027f5f4238838d2b69e75d5230ce0b1517111a349
- transaction
- d1fee959661d499550b34a0fae9a3191c8e8e07474a990986c1275514392b8a1computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 30977
the chainentry 30977
- sealed to the entry before
- a5196574655396c15ab3bd4b50e28ff6246c27e92882e2551746072daadf7c8d
- this leaf
- 5297f3e2e894c9b5d1610d7e0d5cc64fa06fa451654759a4b06fcbd6c43c382e
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- ty8bz6KjQVuM0/oxkCE2o8jaokigbAOxeNFFHJI5eOyijmYVXw2Wry2JC4VS+aQja+FSYvH/Cn4YEu+B4YpxCQ==