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
- 96ace856739c93f8131ea78ae386085074355f3d8de46d5312b75f1740518e6a
- request
- 515b8788c94df438ead4b8edf7b51e407bc45585f343986024a34ed34a106b2a
- transaction
- 8950e0d9d256526a21d91431c979b87e55c69a9f540282826fbf5ad43fad1449computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 30486
the chainentry 30486
- sealed to the entry before
- ac2b0834960464f4ce7c0ab3965a8813a235b0286fa89a6c75de04d6c74650bf
- this leaf
- d781f813fc9a327a778fab66b11f375ec447f9e62177413c996cdf7e78b333e2
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- s0rvoTJxQ6uwjYDw/+hDFN2aHLq6TLtlSLyf3/mFp96fEU/8iKt6j5pbJgRBBY5nwM/K2bl41TOnV+KUQaiECQ==