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
- aebfabd2eaa3047df51e1186af1ab208c33647358557e1091ceb1772adbcfb8a
- request
- 8aaa6f9ed43d27691f2005a43e29cb6864f6dd53511b320b0772cb14adc1c90e
- transaction
- df30981f674586b2d612115a11c0b57e067342cbd59c297c016000bd99d2d3f4computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 77723
the chainentry 77723
- sealed to the entry before
- ca580e9f068a3fd605533ee08e9e93df9bc26fffd7cfe1ab33c5213fb2b7417f
- this leaf
- d32fb0ea1ed30ee72662e954ef883d5e66fd99065e839554cc47d18fdadd68ec
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- BNBMDpusm5IOD7Hdtw5U3d+VkZ5SMMc/IuLTuAHegJN/0wsuypCtA6x0dfVolgGisYZf/zT7WJ0bQNK6Ws9LBg==