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
- aae5992a04dc39b86985543d4a902d10b8a62e305ee8b278ce291755816e5da2
- request
- 44f2b7b3329f68fa8a911ce0738d93c0b26f461a43c8b1e67d87f27f109dac95
- transaction
- 5d0a0a72bc26c4c2af8ab07a822fa2804ff97415ad68f570d280187d0cf87faecomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 45064
the chainentry 45064
- sealed to the entry before
- c13647479b34c26401efb483e2ce25ca0bf42431316b0c9b56d500eb86162b3c
- this leaf
- 47ea62199b177afbd4057caf5c9005e8fa532ddaf44f2bdbbad827418266c309
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- ozKjoOG0NVnXP2S/wycnnKJOQcNrA9rGqBVsDXlZt7h8qN1/S9l95pPVAuTRfRvTREBAMVM9/43EC6YzNRtTDg==