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
- 50a8bdba37bb9f314eeabe050a2bc322d073efdc3eae2df56ea654f5235f4e0f
- request
- 023aad5043ba4e967ad6f2213c02ceb0384c913063830aaa5a96259e675a539b
- transaction
- 49d5af0f30771578cb1257c06d7bc6d3bb7d3b9fbcefa5caad21d5dcb5ca23cbcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 20008
the chainentry 20008
- sealed to the entry before
- 8838370edee373f471f62c58b5f1fb72140f70a18ec9c15e12c32e31d0bd186d
- this leaf
- 1e3f983c200aa70b5fc47b302a01b2c6b3bae24aed39931031f7f875d7d41709
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 8bOT6G6uXy4YEp+k2EviQ6YYdE9cSJJVrbAdHTLCMJpjKN8tnzUZepmXCpdyXE6pPsfAyT3d+GP7mWWMQUPWAg==