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
- b3609d12904cd548b3d5793dc3910ec8736c663eb431fd316aaff499cecaba24
- request
- 8d8a5c73319ad09480f0cd8a39cab5077b21a6000d8c7d3f53d0830b5acf9f63
- transaction
- c145f0bcf45f23688b64b3748f4672502b6a30e558bcb4f6ceaa83206b670bd3computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 41823
the chainentry 41823
- sealed to the entry before
- 2d9690fbd84fbe03d1d5cc05dd8708e131bc30fa7ed178af6d68deac1722f10e
- this leaf
- 2afac489ecc42910390bb41e7c01c61b630c909d79f5d2328d8409c9a57f8fc7
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- K/9Zxlk1roMbktw+xHD0rFwpTxSWMZaAxIyqqgCR4NVSRdgFfhQCM4Si07F5efSA4BRf8ii03Fu2xzeVEULlDQ==