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
- 1662cf1d950018f07d3aa2756137d2b189de72565ba5a3f8bce7e161f90a60fa
- request
- e0ec33c757d43fd893938af6990ff98c75ff03a198e7450b6cc06f8d5ef10760
- transaction
- 44bc5f1162d535bfc1e87e807497bed829f6ea0226c3aaf5f2621c0052eb879bcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 31490
the chainentry 31490
- sealed to the entry before
- b6e1e28006bc962ba87d7f25132e99c883e6f35a6d528d74342c6bf262252a0b
- this leaf
- 5fab845ddcb03d53e0d27636a25cbfc1c914245de18bfb628cc63c400a1334e3
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- tebeMicHFhmRfZXtfyRUG/7vCdfjg4KNnJtKQeO61pXtZkCkiYEBhQtrmrv8+jbrZ8p/IM+soA4quK1R7vWDBw==