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
- 7a12838175616d29b35afd99089d7f30f1156c88bf11176c7625abe2921524ae
- request
- 60135503c113ccfc506cec3fb2592f80f3cedcd9c7679fb19b4ebc683d2f7e4d
- transaction
- 82be80099ea65f84a3ceccebec2d97c79108595d7ccdaa78a095f7f3cc26209acomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 59372
the chainentry 59372
- sealed to the entry before
- 7f62de92bb5d29e25f2e85af3b81bf5b80cf1547ba2ff547859f05e087f5d3f3
- this leaf
- c572fee2846ffa6ddfe98ed7c02ea37d799e80b9852d40d5d1fe671893f7b300
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- SG7OXBmK5CWNkIfU9DLNoUiiqy6+fcjh1XohBx36V/5YUC3RRW4h5Y+i3lhBLxt/qxcKO6t6WVFMA08JEnHeBA==