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
- 3d5476f6041cf52209a9f646f26e84e01689788fdb134064fbd137ebc00504f3
- request
- 1f9890789f2aeaa4062acf405251035f9bd45e0a07449ede5df7320df0be50b2
- transaction
- ce9b305c2b79898615894466cefb588d17d4414c11915db0ac10f9698deec0a2computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 1830
the chainentry 1830
- sealed to the entry before
- 69f454a3f23f73b1b28936ad8072a53c40f39e2d4fee7de5dd5a10f649d7bc77
- this leaf
- 1032e190ad74c65fcbd3f279ad6e18f017ce66c339b47379b24c43e45ecdaaab
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- P4GUF7lQAwN85+i7S3zDsDytoQ0LosAjdlHT3TqAu4ZvMwHVKyaisqHP81JIKnzQjgbggmtuvgWZXFzskYO/Cw==