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
- 83f6426ece9a6e3ed5a7c671e837a1a72162e0da85dbbfef64b1a91a90ef00b5
- request
- 4089b3f7f69a55d5e18c2334ae2448a5fae9c7d9d7e37c75296def2ad7b36a2a
- transaction
- 156e6a4bd20a995f0e2c1379fca9166e1255ea5e852218bd74478081eb548883computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 4375
the chainentry 4375
- sealed to the entry before
- b1c5e36ef52b9f75c31f92f8ce20abf85f6c5bcfa5b572b99c28dd91110b2a0f
- this leaf
- 18026a727d93f402740222cd6e5045171e05afc3721fca3969c23c8de0b66f6a
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- mH7njUzyOqD34qCJdU4rW53GuR3fybx3v8izkzEGAudz5Qv1dI53T3+csH4c1v/T9JCS+b7BUNXeAPGsxOAaBA==