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
- cfd4e20591cd84289999366b223296bc59f51cecc296348a0f891f92672dd206
- request
- eb0c2f34486483b18284e6e4990f96acd1902a7656cd3b7c4b05527dd42dd4f0
- transaction
- 10bf9c33f197d9d9b601dfcfe9560580eeaf14150f84c52d195b4ed06aa12111computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 7844
the chainentry 7844
- sealed to the entry before
- 97fc56b8f2768524f4e0c46c46a962edc43903edd2f796ff507a17c57a4fad81
- this leaf
- 08665c2ec9a45e5ca78909050b009113a55bd562f505c0003b7db1f603af7b7d
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 6RRZM/xXGBp30EIylrmFy4BRYVvLnDzkC7O4iY456rWoOObsMfE92XZJXDjtkhaRYt/u3oNAvz0XxdxQUc36Dw==