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
- 3586a96a0f922c187d838784809a6e18d171bcd59bb7ae65d4154b335a7ad2f3
- request
- 4241962af3296136e9ce27b1f174f9821d8114e7a33d1de65cd1ad93a4fbee2f
- transaction
- 2279bb4f8e713fa70d615da9d88eadb734184cefe0ee42646a303cb2e37bb19bcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 45630
the chainentry 45630
- sealed to the entry before
- 8e5fce6adcb911624becf759fdd5a1c6a00a2e360438eb0b39a2420975ec0c61
- this leaf
- f1f17a7d1f5878c3a689586e602500a243296a259f52026fb854e24be3d28991
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 2fg9tMfAo/qJhsyHzlUPFZqnuQcdtQ04CtutSRfAlkSqfUgk2XSMo4OacxBFP+KJykTFzvWURGIPFFw+K0aLBQ==