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
- 15342c54408d421fdb013a54b6722d149e9e578e7be043f21cc1f904317fbf0e
- request
- a756ec3e6324b305e67dd1fd0a1ae73fbb7cbd1ad36a598bbcf90074dbc50bbd
- transaction
- 8cfa4c41b875a1bc35fc78371b76e688a70f00cd9dce3f6601cae03f0f27562bcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 5507
the chainentry 5507
- sealed to the entry before
- e4157f2c06810d57054c69f96a774414a472f57e72c281c2763fd704abe5818d
- this leaf
- 26bca0bf40d55a61eeff1d50baaa5f58c652a7c18b128b54d2f59b95ddb2cc55
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 0FcpsLHqvDf7YpV5Q0UbkvI29fVjKrF4Cc6S75pCAOSMbL8EoP8URW8CIMHOdR/cA2AGXRE5T6kCs5WiZMAmAQ==