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
- 4702542dd014a486f35b4077b5521468a614a4777a58b802e74a8d8c2fd1aec2
- request
- 5a734e8ef4e42e13831abca9e6d23b3ebac335ea3c89fbc2f60e01ddfc19d1d9
- transaction
- 534df52d521cc6bd29e552d8db875c1362ab67f1214cca621802efe60ad9433ecomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 8388
the chainentry 8388
- sealed to the entry before
- 065b88a92f7eef78a13ea28cb8f3c9eb2d84212c3218db298a1f24a427f4a2b2
- this leaf
- be52661361fc319e861445523a410eaf3d8b1ff2029d1f01f6f659aa8fc8c6f9
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- JQP0Ea0tJlnElCu2seHQeXTOR7M6rRj/xjHfyoKBqz88r16OKTjLqFuwaNTjG1iF2DlV+55x8QkaQ2BN2X5RCQ==