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
- 288e478d1b89e7ebb0f5ee909a9f2395c329461e1cddc7dbefa7286a7cd1573a
- request
- e503ef99727ca80c6d89a7dbc6033c15bda415fb59e2648205439ff204eb2238
- transaction
- c7449b10c20ad37f7614d9e235d2cd18c7b2fe2b074e80ef86e651443859a0d5computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 69225
the chainentry 69225
- sealed to the entry before
- 2c095c7587bce9f4f8f06f3eac800e1831539979ee65bc3cd62f1a363521e85a
- this leaf
- ef358061b1bf473f52cece7dad8f0176443fcd13293262703298b86ea39af2da
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- IoOWVW9zSENbTZz7m2CV/GUuvhnbToLM2Ji0lkZVhHvu1ldUQe1w8qF/PuNG7WE9eQ2VONc/Nt8EziphbBG4DA==