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
- 6bb3c0ae9c726aac81e6ca14c1d22f531a061b543916b1c14dbcb5988b54ef46
- request
- ee9c32492d225b1c031231f1f968377965efd8cccdb7b3024178f4801016f0e5
- transaction
- fe8c49c5f898cdebbbedcd98deea78ed795906bba137f3dfc61e45e63bd4d97acomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 13318
the chainentry 13318
- sealed to the entry before
- f7871ff30080693cff516bebb801f877f1095d4b9d048e9540e77fd338b68131
- this leaf
- 84b7fdcd35ecd79ea1dcbaab2e65bc8ed56e67e3c4d2d2c7aa5b6c984fb2ae61
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- sDCvSdw3tq8fdi+aG41sUOxv86YxcaLjssz7Rz92y7JoMygsDvVgy1kbLjwwYRUaHuwq7fdA6M97fkYngEZmBw==