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
- 2cf23c55a86e555691137e78965b69bdff1c6c302a9dd8b1675ec5c33e5a6330
- request
- ac91ea125a96af81fdd40a7aa72e731c7470000c8806ba82c5934617ce3d4d70
- transaction
- e8a437acb7656321a687d99bb96a1f611f224197f1abc30a094c6d2ba1e41a5ecomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 38225
the chainentry 38225
- sealed to the entry before
- 36871e16409ee2b56a3efea71fc1dacbb765fd3b7fd0d25a0f65f9d29f2c329b
- this leaf
- b3adcdd39fe1bac62c5080f02abd2fd751df9f5363776ca2f0bd7609aba8e050
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 77wM3J2eywkThL1tLzmgNZzZuZCq64ZqJmEKF+9P9Ehw9ljSDOxYb1z7vKGuEMvYjFt41+Ax8U426uqUTY1pCg==