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
- 4c765c2ed4e9b708fc0faead0a212d9febbc25113da4f29e822e26a40891ba16
- request
- 9d079ad0d3923f52404ec71a45a5ecbc4ff4c6df8cc242e4134cf23afec75dbb
- transaction
- 14c63801b37d6ed09e4372a4744335e3ce4ca0e4b4bca503be359dd62cc75b72computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 71435
the chainentry 71435
- sealed to the entry before
- 468fa9d77d996d80548879ec10f7e26188389b54e75bfaf13044cf5c3991284a
- this leaf
- 3363bde3460f928c107aaa531f4d11a9e35ddf16143dbf455bca695389dd7846
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- nPZD1fTTXrkH9pKOXyHrl3iizW9jqzwSHLqJPKKm/I7XYy7fqJbTZJWHSXbgz2g8YrJ5T/t1ve/O7LalUzjhCA==