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
- 42150d02cc36b217f7f537c4a35e0e38e3152a73ff742a792969e637b61a40d8
- request
- c15fdd6c7328506c04341d67fe79422b6bcb0817cebbcef5ddf021624ba62cad
- transaction
- 57e0de0e15762f8503dcb5c8252001c814942f4d0004145c71eae7fc3e869296computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 2220
the chainentry 2220
- sealed to the entry before
- 39b50ae3212296e49bba64ee75bde64579843b366d625a4cae1df85f55d16851
- this leaf
- 3f41997ac18086bb22e55b81cf8661724bacdb51b93d87a276e96ef96f47943f
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- Hz0q1Oduv7oXs70QI5v1pbkyQaj6eKr5YkH+YStz34AYe0yh5me8ouOdZjGkm9a/h52qnytEHCZM6j3hVWrSCw==