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
- 06d7e09e4c965eac2c8a57b2225ac5fe015068303bb4c96436d8a8f881264e56
- request
- e409415ca423a5f7ebc8d13915bbc74f37a6364ce31cc08edb05af7532cb2246
- transaction
- 27c492e0ebb65b7880dda4baffe82fb77088bd4a53833740792090a20279f38acomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 30041
the chainentry 30041
- sealed to the entry before
- 64b8fd4d67828e7893f814afcbad0ddd18cd331abf1c865633acc4fc6fbbbfc7
- this leaf
- 6d63f4cb271b6bd03052f29c8706ae7a3aeaa70a6db5884119b18096440abda0
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- MfxI5c/vabq6ot7CoNxsXiXUlgPAicH4kAHXF+dqBMsc5vvpIAvcQUMpQdVpbOGOo4MAiPOufxipgwOd3PjFCA==