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
- e749d0dd2d9c593d8d950cb7939e3234af8c29ad24e184f13299a719ddbda32a
- request
- 0dc4cc0a6d572d3100b8a04fe149cbc0f57e308a4ac995c41fdcfc29af6315f9
- transaction
- 384fc33a9c0ad3a0134c6a17a444241d0f95a20ebab4a6ba7fdc5e81a5f77573computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 35456
the chainentry 35456
- sealed to the entry before
- bd57a055f755a6636c1e8b2629baa32946f17328949e01926f78f8ffc2de4fa5
- this leaf
- e9eefcbc3ed38fdd7e76e1f258788803c67c2a849d13b4734cc670f3ac46a293
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- ME25CBHREEVBQ/sXEDM1dyF2mNCzkL2YH680ECyxxpFbaG5JLuEk7JrgDi5HmubI99u/YpbyTR9Ow7TqKt0xDQ==