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
- 6714ee0bc07056848ec7f3ab650dee16f5b323840e835b11c2c56945e4cd0809
- request
- db1279d20c3ff8cc3c92a2158cf2a7fe8ee1efbecf2548b64823ba8a1ac62066
- transaction
- c69778913f5fd48c6ce1cba5dd913d201f1e63061b68d533ad89d112d0e5e9eecomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 10095
the chainentry 10095
- sealed to the entry before
- b66e6a7bec03121ed29406657dcb3228cde17cf7c36b0b5b7e982f8509ff5230
- this leaf
- a33e72f8e3b114ef2fd837ababa6a0553aa7af51f2e93e6226b4ddb1e4433b03
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- VXEsjrZ5FlpdzTejQbrUu3c6RYGIEpnIT3/+WK+MVtbva9xGr/rDQ7lihDo9Hj5stwG6yMpP3Npp2RR/uiNpAg==