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
- 10c4ce705c636adc811cceacc834d141bef431286fd25d8d784902ab48c819c1
- request
- 9d871bcb3423265ca3893bf1a285f8607ddf508234d84251c2ad7b66cdf59aef
- transaction
- 5506cc39cb435cbad0ff10101be547dd8b75c66c09335edac29f78aff6b84f4acomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 35357
the chainentry 35357
- sealed to the entry before
- f959bfbb3b61af9b89c1dbfb7042bdea5ce2893b695b2af7c95730ecfffaec0a
- this leaf
- 460e0615a2b32ea0cd1b555469bba6c0d389019c0759dffaa35a8669e7756350
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- SGlzaaDkmTuOfsdcQDJpvBaUpFWQCzIWu0amDKojbOORdrC+okQmCmp9bGGej7DY9jbf+Djo+dGPZzMAxGeDBw==