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
- 5d9f3d99672c35ade6cb0f74f8412f5a2a9cb2877327010f92806040fa1c88df
- request
- 37d21137e8c3c54f96e5f4437d94c00de2aef09519c7b2e083b224feb687fdb5
- transaction
- 8d83d947d6ce643700717a8a759f3a2add7324eaab85089ec210aa3dd753f4eecomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 33446
the chainentry 33446
- sealed to the entry before
- 21950e6135c981f9ebcd3fa6ee26dd997e1df490ce6a0098e053a57a424d90c5
- this leaf
- 760b73d8ca09f880401b069a8c1bf52dd02024f12a0e7b3281722095c2401533
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- XtLcDUb+aR4Ij+hhH7QmU9z9+X2YOCJ44fjyenv5/Uoi5UOKakBsD3hCCJj3qviZBFX3YB7MhpoZinbSnXnbDA==