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
- ed8a80e98b87c568a747ef3d43429913921572ca8982e9266dca0094bc075234
- request
- 528fb163ede081e2503dcb00e63e7b38ec72c3bfea8732db6fe6956a07ee504f
- transaction
- 646f14c7e4484c89358e267b1e19de0435d71c450936cd585ac231ac13307788computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 2330
the chainentry 2330
- sealed to the entry before
- 518126296cc3960adaa2a156fd730318cba9d37c70436c50c3fa2664a72dbbc6
- this leaf
- f20944c4c77f68d11978ecc3906d5d299efdfc76ae5a2e15994acda9c4c60007
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- R3VWAUKjR0C/0WGLc9UmoHrp4av1MwrocTuFiA/SuAvQqVEAeJHIbfCh/fmZUW9LbXryIJaeI0RsFn3a4ZdVBQ==