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
- 7fa70784499c603adcaba03a0bf35ef53bc7485c8a517e01a7f48b58aaa4779c
- request
- 77a946cd78cb94f2b84b155edd45fea78b6a733df3423b03933614b9a3e96383
- transaction
- 9be93676210724b7b7604b7eef33b7498da7ece8e5d94ab6598eadc7d756b75ecomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 60128
the chainentry 60128
- sealed to the entry before
- 9cd8bd847355b0856910d5f3eef67cc1997a3b3e57667be27dd797d5702bf443
- this leaf
- bb4ca5deaf361c91183bfbdb9f5bd014ec6981c770deb5e0ef93359bf0b12b9a
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 8ipWKRixm1lIdzw8Wy6/8UoSPyVZmwJxr52g1dHsDpeIaVnt5WkQyJtE+NQVUTefRgovEvv9gFz0EbrZzg/cBQ==