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
- 9ab1ccf98fe5c65ddcd9c2eeafa2c429fa855ead0f9258b39fd0043a3b93d78f
- request
- f0a960373464a1955bdb67b109595f1dad72b72f2ec64e41de63ff598fe89636
- transaction
- 714a7bc6bf17461647d548d16175a8291ec626e09fcf34149f683739b7458f0fcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 48555
the chainentry 48555
- sealed to the entry before
- c072f06e82550cfb569e669ef3e270bce3f8a3970c22012f659907a16fb0ff84
- this leaf
- c3a2be31cc1960775dca7554312c465e867051f8df6161c662b3f525a83d9a2a
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 1KhKhrMN6yN57SVB8pwWSeD+/dv5ZhGlf12rUtXlbRiOD6G0CJqDTWOUEFiLyY6RkPG7QiWPac77DwSUGkjGCA==