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
- 7933bea739f3214847242d202b978c06e6342305d053287a4d3bd5f30293aef0
- request
- 0d628b68cd0cc8e5dfcb82dc9398c0e59b55000d70661dcd0996b15ed2276bba
- transaction
- 303a0c92f2c46b5f8c8a9cb22795456d35c371732c4b0cbbd4e7e4bdbb1b4b61computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 76573
the chainentry 76573
- sealed to the entry before
- 569468bb52991ca3a7dd8239be54933b0bb959ad1beeec90a1ca47baf650b3b8
- this leaf
- 564896fe56f97dc140e5048517323bcfd50ca0c9bf0b8942cf41f4bdcefc6785
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- e3C/x0WBJo8I8VVHyy+yfXJP+JalJm0wbo/Yn5UnkRTT5xwSv8TC2ktDvDgI+vvJs1UG2n6enDFkBPVmmN7jBQ==