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
- d0e03a963bfd88dc3015718e5dfa0875eecb77cc189eeb18e27a07b8e8f3c72f
- request
- ad66bb6cb0f6529b6fceca0a5f5e081f8fbba6344b46a0cf992d8694d55bdb5a
- transaction
- a52919edf87d04149b77364d0bfdddf0eac7be6c88f9c0cef24c8b28d757ca7acomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 44163
the chainentry 44163
- sealed to the entry before
- 16fc82093474ecc9143dd9e7e4adf84df1b82d34c59f8465c68d02382c854f16
- this leaf
- 61fa5dbd7fa3984a760ac48f012e74aeb1613cc9468382cf7dff289663a29bb0
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- cYvxbzDckYR6de5cfVM7cPdZ021OTYTDK3W6LPYHrOcdKoDXfq3CTQTn+j7RRq9CUAyziV5YFXmZ5IVolaViBQ==