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
- 2005bce21a60014ede9d7276c3427a045d609aacb958b0b654f3c373e3b67178
- request
- 7420ec051308c8c4fc160024ce9e5fd46d16976e2b1997ab85e17b19a5e9b253
- transaction
- 15bd1bc3939e0ce882797dbc28ffa63c392fb24c028eafaef42daa767f97df83computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 11669
the chainentry 11669
- sealed to the entry before
- 64e353fcc3c3ba5780bcc3b4877b617edd234272f2d61070b3be97f9b989a0c7
- this leaf
- 491966f3c7ac87572f8b2c57fd21ef9174284f2d9f440fe64214224f9cefb686
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 1IqWG4njWKLMjbFEN/NWM8957IbM+5gYP9W7z1rWwmR+OszTZfdQW1myUs18Jo89jrF4cuzBjbSQrOOjJUpADg==