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
- f54c92a3ab1a3d73c914aa57269d6df122e3dc52a4fcd479a45d613071644dc1
- request
- 55f564d3ddaae8748a0a82a9b01829233272548455d7e2e01eef336d01809a03
- transaction
- b2fa0b783e37dab0cc98d93c6461ef6746c5b5563df59facf197c078c204b548computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 1805
the chainentry 1805
- sealed to the entry before
- 231a85e039e81f416dfe731681b8e629988b3730c62bc249c655a744c51cf35e
- this leaf
- e265f9286d0a5cad0a9e3fc7c0e4dea6d5fddda05aa1fbdf6466105b336aca9f
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- EHyXgwjRzMJr/3wTsMrEX2GjtnzvO93AZZhMUsFolHD6qb0dYhBbDNhM+N10IXmdVTwZiStTVklcM7x15uRmAg==