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
- 0359003125556b684227a12ec176201aa2fc1a5c130abb9d8922e383fcce038c
- request
- df0a82d9d91aa17d6335568c4a4cfc34229595670a7aa4f45c80c964d6fc7ca2
- transaction
- 0cebaa4aad1326ecb6c20103a9bd3f43a0e71539a534ca182260e2cb7d1f1847computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 51264
the chainentry 51264
- sealed to the entry before
- f71b3382a327d9e81bdcece2ef5a12d24aeabc52b3ff17b6d55d0384e934c83b
- this leaf
- 998475a48fc223f321d2737ef89aaf59c7f028f42671dfded1f3e51bb97ea490
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- EV+hFeoZEmdzAh3Fh34VopBt621NiwRaUEQeP7fHvjM19Z4RHEm3GHVE2ckAdESocwdiyHkNEMr0MFCrhu7LDA==