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
- 3280c384d5cd1b20700d42c195894350a95b546c09e377b0b1097b4ffdedb287
- request
- 7348c9d70702420a7796205ed3bd580fd0e456533a3e5c183dbef94ee7dac5a5
- transaction
- c6355b5a9e87a28fbad00aaa0d79917b4daa6970bd0175a567253ceb80fbea46computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 49568
the chainentry 49568
- sealed to the entry before
- a7a717a2e5052823b96d06e321ba205476610dd0f2cca90956894e8ac2d81603
- this leaf
- d44e7aa04c01eefff0d66c14827990bb873dcc81cf5a6cbef166cd4e01b45d73
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- fooGzcDeln4N18gq/M5QTHDK7hHKNdiqqL6eLmbDN3JP8C9qb3IYSm6KIKtT2Uxz0CV4QIVGotpVjoNrHlDGBA==