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
- c6d01bf807de20598d84aa7164d9bdd4f8914f80783236a8d85e2979d749d12e
- request
- abe7d4f54f7e6274610f4e76738313136554c963e51f200fd7dc5f83a92ff225
- transaction
- 1c377985c1c636bc26df63fe6f9eec4e905f25f95a6e9b5ab5faa88f1a6feb00computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 42143
the chainentry 42143
- sealed to the entry before
- cc4f16c99a7fa47020f8f190c34d1c40be33520e92164ae599f63bb5b3a66cf1
- this leaf
- e9062f24550fc60cd2cfee6529061cd39b3fc8aa34dbc50a4638ce7d1aef7e4a
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 3XAKpQzcndG4ZCl5GlX2cXcRjaFrVGXmyDQ2xoR8lsyw4yliomWOBahI/XEOwxtco2SReHOCo2F0RQgqWA7UCQ==