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
- 1604dea095d576f421b3ba34a9890ad9f040419c9a2864fb76a6c2cf7e08be56
- request
- 614724219ef0e31e344bb47445b90c446ddcddc267b41d2b1ce90823fa3ffdf5
- transaction
- 918fcf5544fc2d26ff19d5a22a88a437e8174ea65662fcf88157794738ea7c9acomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 2070
the chainentry 2070
- sealed to the entry before
- d4d7f22f85ff3f2d46b98e5285c4f1c0cba94e003bfb9256afb552e5f2da7710
- this leaf
- 0fb5a03e38e9647aec3016a6b29fee3b3390fa74a1ad20f571d191cb0c01eadc
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- fAjqna5efsjOgV5OdZ4DNbG0iNESd6pbkygvBrsf+o3Fpztytc5THOw6Nyi9acp+JslZQ31PVdeWUASOCjhdDQ==