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
- 7b6c43cf53a611eade8bb813179d597f13f7d8df33450eb429e1fcf3dfa88881
- request
- 1a9518585c4f7a3fe5837a47051e9485efbb892016ace45ce140dada040ec807
- transaction
- 01dee4946b85ed53af78b6be99229ecc26cadd386fb67c1877a0412ffbb1e19ecomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 26853
the chainentry 26853
- sealed to the entry before
- 413d2361d16d688db927d7a92481007b333c1be94ddd81107a4ac2f55531171f
- this leaf
- 1320e73876ec4bf447f3e3f2e339ffecb364414a4ccc4493751fcebe37175ff1
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- k8p8vvKLVnUq7M2tCL3bc+b+PVrBasAqLxsc28Kg0Jsvy9wiZfEDrIobEKjJzoPkaDxA5q0VVVHZrqfKKtM5DQ==