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
- 54a7935d837a3272178a7ea0e44f6129ad5f39354c5ad8b7a14e5be340eff6c2
- request
- f137d52e8aa45324fa48392443cd3f0c188dd990ee2fb405df942be8ca039670
- transaction
- 8fe8d2e039dff6b9b238e0377d1bae9e19432bdad876b803bdfe5c973355774dcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 7803
the chainentry 7803
- sealed to the entry before
- 2fabb0a8cba0b2fd67fd4d247ae125e613bb816e188c74d5070eece76f0e1ff2
- this leaf
- 97a0ad4e883172aa79bb748f6096a2e22452498fb8767bd481e15917a23ae60c
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- c0PLiZD9x4CdPQuLUnY5fl/DQjHDE6v/sc5KWNT+HeLxE9LmNyjq8q0OAb3KnpHGRleu6L5S9bBEtvupVKBEAA==