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
- 344f66f0ab46a86bbb2d47b02255d94df90780abf92f99bf5c4298ea76aa8c06
- request
- a3d7bd27ac653511cfac6cf1bff6c2160220bb60c3f062a7d84ac28013ddb7f4
- transaction
- c53bfd5ac6903cd1ea29c438f93a40d69b24da1a083d759cfbeb3c601b17dd40computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 40491
the chainentry 40491
- sealed to the entry before
- b22eb9d47735c4841b92f98842d79d358a9fa9d9b2edd004fc938e5f76366757
- this leaf
- 5ad96d54c3f5a57cb1f04e5cfc06cdbebb01e2ff2e0e7f8f2eafafa0d67f1531
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- bPrfsZQgi/gLSsNEkTNSGIXu1xFhoiTRwgtASsptpw+shIWoIHoYmd3C88LR8uh0fKc6hBOdcRsAZZ/V+DPCBg==