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
- e21441d64ad99ed2dfe28e616fdec5cb09a6cf94e74c72736cac1b2b2bb36fdf
- request
- 577c1f5f31d39e52da79e844b5f3798714543499831ba4f08deb9ac9ebec25b3
- transaction
- eb4c25d469defb0e3ede6cc702b982046f13fea82a3487fad443a56094818c67computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 39374
the chainentry 39374
- sealed to the entry before
- 3006f7a0cffbb389d3d6f40a3df94905b307684c902aca80ec8fc93f53f48c9e
- this leaf
- 880423ec8b1f9e8877c6661a841ffc51875696f7e59b1ab957f390fa9b543e36
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 2+iEpKyzH+oZHLVCOolRwKc0cr+6mN41BsHyf8E47HMZ0lVgFnmVlbKJ2vnFX6i7U5nGuT0SQ/BA/uetXdB4BQ==