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
- 8b8f6ab3d472cdb4cbdd9b957be289023ac4e87d3fbab9532cd6dcabf023d67e
- request
- f524391fcf3da7462e4ec60f24133c4e0bf0a7432143618f36fec6ef5281dc22
- transaction
- 14150fccc0753ea382b5b33dc2fd2c43c9815f3edf83c442290cfe5ceb79843dcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 10272
the chainentry 10272
- sealed to the entry before
- 03e9a1217ce3c29833a4c68694dbaa97641fbd50cf12e5fe735f8c706ea4d0a7
- this leaf
- d6060dba96253053456513323d3a2c5adbcf10d43cd0a7a7857da607320d2fd0
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- RqPctYoloI6iC7OaVC57TulZOp/I9XV+VDmcC64r8o8hs8t/UuK8SXcbgoUSKw+uFQrXJ8+5pEE6UQlbpTSYDA==