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
- bed1257ca4d26b80ed9a23868fd34ed70ef1e6133191a6b56f1551319ff043aa
- request
- dc40ec4bd9defd65916a0441a282204260b18d5b1b05158e24331e9b81b8f6c0
- transaction
- 1480948db8469142379f5b815468157bf23cd443c7386ac67789df0c7ac36a2bcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 49522
the chainentry 49522
- sealed to the entry before
- e5f79061eaddbc9473b425dfb0f3e93b78fac02b36ef3bf5a5f0612aa9c8e404
- this leaf
- 4c496aad8b836a9398537f00d85b569a22f1d97a8b8690bf8234a4d78772b61f
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- aRzzKBwSVg/PKswyzRFufrIhIGQdce9XWiGtLsuDxSGbL0bqyrzowal4LywVjWN/mJTqQhNrfT/Q4i/hfSIYBw==