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
- 75fd27fa5b2ff19df695724bf31c683317929513e45e4d8956f8897802496676
- request
- 33ca83d7899f8cfdf496aeaeb6a99c2fca191baf0fa4d465c881b0e2b6011a89
- transaction
- 8eb07340dac79fb98f0fe07d28e6584f1c59de58b530fe6c2532c01fda3036eecomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 29168
the chainentry 29168
- sealed to the entry before
- dbdf36fc2bab1e95214a87ab214e465f7edf8b4dac398b93e0fba59b8fd5cedf
- this leaf
- b164aec8cb790173c93f74dc73bd069e7b4487345a3f3363fbb85843b0a6e389
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- QqUG+nsUUA4vifWVpcpZm1BU5uHUEae5S2+69nkFu0h/5xdixlZoloQcZyzOIJaepugyFFFt6OVNFoPcp+1QDw==