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
- 40f35a0ba386f33a966eb42b942ad1b518c91955b4823f7e997f366a00b2b881
- request
- ea12fc174a521f4abf7ee367e70a9838d02379df344c43d5227e26e03f091d0a
- transaction
- ca3ece26d5dcfb08f7d55f747a2325aa53a1e7304334449338a80a18712d6faecomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 72893
the chainentry 72893
- sealed to the entry before
- 5aa213d51ce8837032e1b18e89e4757fd364d4a868e11b57e1b5643e74716311
- this leaf
- 1779ad53018b01f2c92809aa6753b573880bc45af261b45af8b4a76822712eeb
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- iGNaj/TnMvrNAk+40lMBpKYbtV4ynUrtLi5aaA6LDldKfBC8X9rPvDTRa5g66KNBxaUMtGFU1A2lctTOrZFlBw==