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
- 4cb4e8ae75ed220efbe76bd1d9b42f185048f1ff24e09f00c50214d0c9fd95c8
- request
- ed0c958daa441df3f796e01664c553ba4eae14da3fcfac0bc2448ba7f2cdbe5d
- transaction
- 38fd0f5bdd5d721629f92b2962621522d8afd54262aaf0b4ec85af8e774f1fddcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 74473
the chainentry 74473
- sealed to the entry before
- 36bbbfde1b2afc83e7533320e3ff495f1cb81b41d1d2efb4878a2d47111d7569
- this leaf
- 85442cc654986055ffb18ec3b8ea8556dddd1f0a651168152ea8d3d86e28ea5f
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 1mP0UNfg4paGhzDY4wa0F3BYCRKgvIQdlAsZMkk4HRPPifMBxA9HOawcM9OgMLYOF036IvHvZF5/XXEjnD7yBg==