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
- cd537fed243eae195d3583970b7bc1de2387a73efada89d1551f1f8587744c2a
- request
- 0c75b51a1b6467a4df311db7f3f7ee85d63f387487d51720166463ad974f6673
- transaction
- 7c51cfec8fbd10e0d9713edc157d27657e2fb83580dc79377739e20edbfb4aa2computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 16624
the chainentry 16624
- sealed to the entry before
- 686c1866bd0fe8be53cbbb55b68ce8f7681c9dd2788b8f2fb8de956200cd67e6
- this leaf
- e29ae4843000b83df7aa06c6461e8324ea20bb034c0a79f3016fd7be2640e711
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- evAzG3fje9lNEC6W2Q/gMX1D8ff5DTsGBw4zemMdhOJywYnf3+PXOqiBOe42qRsA8LW63jLqxM0jk8wCAAJWDw==