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
- 7f7944dddd2990ea7f35e7f73bbd84ccce86030c454bd8dd7fba72d0a8cd7183
- request
- 47387b30215e794835b74868da939a39d536e02613868b17f963208f58a253e3
- transaction
- 122558daf7b6e14fb0b62e4badeabcc545fc960db9757b7909bac11c559e89facomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 9659
the chainentry 9659
- sealed to the entry before
- 32802011d46d904b7b802a196d865d0e337f3c1052daf2ac8568b31015217cfb
- this leaf
- 745feb9ae477a587e17fd3898fee86e98663cb15eaafbb1e7b08ebe26d8942a7
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- sMJ9yXOsNC77ZWvYpVRCLBFO/sMdfYKeCe0N+XXXK0y8n7bXP0PZ0p/qOfSQSKOCNSbGcKIjsusW07iAXu3XDg==