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
- 1e38dc7a6ee161ed1b8d8d42e33ee4776ce0537aa94f44d5a261349783f3ea15
- request
- 07ea90de9e33398bffd4dbd80476ddaa0f6cf66d2e9e3c85235b45746bf3b85a
- transaction
- 51b23e3dd8325c3efb06574370bd32bb91d94fa1b303e27733b8609ab3ec301fcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 70436
the chainentry 70436
- sealed to the entry before
- 93210a61b80ae23449f8993a0e9be463adb9b2a1da774954ca56bf7b8428eac4
- this leaf
- e2e5980082a6068447d6d8122f327f22e64d000542663c56d6d7648c838160ae
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- k6KknVNE5wB4YDlly6VPn3IZcgDNyrO/DystWwZ0YMEh9PgZj9pR5SEYkvYQeFqrGLcSDbXRv+Z+F54NH7zvBA==