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
- a15feefecda78cefafdfa089cc605bb933a0a7878fc26d6dc1355225ae102a78
- request
- 08b2265fa638f6f42cd44b696e689aeab3e1f37e5441b64d7f89e7268566f909
- transaction
- 229bda0414d2124efec0079bc37fb7a17cd61e1a800d4d98c09a4656c3b8a1e2computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 26024
the chainentry 26024
- sealed to the entry before
- 47b5bf21fa7cadaa70a0c63811a2d030276aba85c76d70da2f6547db22e38bab
- this leaf
- 18478e366e3ccff6cee3ce382f4b574575d09abe01e9f5d884954253fa253557
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- +/gFfssxG9VVvk4P/Daaz1ZXmLNgAFqA9PddSM9oRXCzNvHPwgMUV+USMZsO7h9LkVIujMnaMRbYNVH9vCDSBQ==