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
- d54c41abf9831926e7344f70b4627e3163b709861fbeb1e0399e91a9ceeb2e33
- request
- bae207ec5993ac603e923a53287616e1d42cec3383d1c4042243658a0ee48825
- transaction
- 9bd3e21f7b18f604480c7e488e24419a5fa4f2849889248b4f24aeb865a723f0computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 58670
the chainentry 58670
- sealed to the entry before
- ae0be9063ca0f7eb251d043762680d76056738bed15908a8e6d596cad10e9030
- this leaf
- d685d778d47899a3167cf11b96965feda6440e2f4481b14d7427402d265e196d
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- QqvKS2yhVi/KEGhIPX8B04X6iRcjzc/lfg/HO12LeCHV4BkI3i2W9hxNxaGWV+mtQjwy0RARGzTaH3qJqfmjAg==