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
- 173d28884b5c23ed630f0b69c6b6843a8515d52b9eda7e9fccfce77ffbee80e1
- request
- 4662d6525b8ac8fce330d2b21ea56f3ccacf818d91e690467f71da9300c4c653
- transaction
- 99c75b5598216f4de2a1da1a94cb7696d0dbf56ea7f2882892f60039b942e03fcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 24574
the chainentry 24574
- sealed to the entry before
- 06ba57d1a664b55f05d4ac466b8b32e65cc5199fd99d43207a72fe833ff13cc8
- this leaf
- 0c39ac0e212ff940f7712322733af96d7a0e2821ae01b6a451b063931c5bd255
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 4Dtx6fFxouCbOwWFN06yha2eby0kyoBg5dhD4d/GpQPoH4JPZdXjGZkYU1/mhehMt0olcdw19/6TEzyJumnfDQ==