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
- c365acd3e8d5470fd4da2d5f5175a706f81a2f6a7346e51065a91698be01caf7
- request
- 21a40ceabc59265c467a8bef91dac309cc3de0e77e6c7f0f9c552d53aa16c9ad
- transaction
- 1dac38deeba48cf9da96d69ad821c86ee44dac58cab45b88af8ad2d5716a6d11computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 36604
the chainentry 36604
- sealed to the entry before
- 8d555cdb4d548e5d7062f1eec8cc0047be93af43838efd945e01e908761883e9
- this leaf
- 52a4ecb35f4f39b6900385bd30391d99ce1f7152888d0e62a71d39833fc0baf1
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 7XJ27gyTe3Pzm8MmiB5JZ+j2/jPKS6UN1XK2gRbarr0mkNa1eTpU7efqdOMFrkm2yoL+9MEL0/B8DwOtwuc6Bw==