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
- cb8b174ab068b4570a05794ee0bfeb0bf13c9818ae9158cbe610ac763643e582
- request
- dbcc37cf361c4833dd1e5cf057f2a92a3c87217637493bbe1e14db75d73f7a9f
- transaction
- 8e79e724f82c522eb066fecc15850b89602822a0537e38f88ec2f646e298b1dfcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 20878
the chainentry 20878
- sealed to the entry before
- 84b85ca7344e76dfd81638dc042894b16da2703a74dc7a849773154e4143d63a
- this leaf
- 3ef306e3d6458f9bc918a61546c0aa59aa369b1ff2b0bf0f3a96177da4caae0b
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- awb1ZkgkYwmWczr5fA+tlujorVzHgC3IaVVa2pDXDzw/wSutX3+VED1Glt8qg8KGGw4fDCBtmqowLkO74oblBQ==