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
- a8542e28687b26aaa530b49b2e14cdcbf20ee8df84d55a99b2220c6d31324b30
- request
- 0f794d87c725bbb02800eb79a748f2bd627dc9f36a90feb857208a27cb9c120c
- transaction
- e940657c749920507f2606b5eca7bcf8c39840afb9ff6b6dc50f080c18bf4d6bcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 60590
the chainentry 60590
- sealed to the entry before
- 1618b6f37045fa78b5e23463a18e3ac11a95a6965dc06bd59d99c2de991f5ca8
- this leaf
- 60d82e4601c21d8d1d93937d58c27980c1f2ac88b714910ab37e5ddeb6937fcb
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- bgaxFa2KvwSjYQsV2Gf5bZb6v8N9KShUZQzQjtV0M6xGqnYRQhrVT2HluBT11Xm4iWJg5a6T4XSeTkWbjKG1Cw==