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
- 959fc7e2a392b5e16f4dee60bbc637b5947235b3422f29b0a2f8a320140e87a9
- request
- 50e2593de5f5557aa474b2319082cc8d8b5c717e44ff7d373bf298e19d21811a
- transaction
- 33fdf962a50b3f8a6c05d2862397a082023c289d6da14fb713a77bcbde29c38ecomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 54370
the chainentry 54370
- sealed to the entry before
- 7412d0e37022ed9929c0ffb631171d15ce4b5fe0a72d240630a0738d3ab7bacf
- this leaf
- 6d43d308df022eef6c7bd0b532237a46147e69b7953f38d374869cba23c8f651
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 37te1NMF20uSEfkIvaEJDb6Gvs7h6G7LYA4LXajIOBdSyF43yg9lpKgXPl/4HNh6KuFD09C1zu/TzPkKajBRDQ==