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
- af5bfda21f60c97eb65157fa71dff15f89ffe84db693eec636fd94fa03cad0bc
- request
- 7c47eb79ef9828d5d1cf34ee805227a5b14a30e521704496ee2d4eb5fecfa98c
- transaction
- f0259df5cb577c67abb3549a982cfdaf299e1c2588051848c2c3e0f02188c80dcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 31993
the chainentry 31993
- sealed to the entry before
- 93f5eae8468435c3193e7ff8cf17a255df02b342cd0a5ffcbc002d0e60f07af7
- this leaf
- ac9294f004ffdf750719c5104048b9f8def34e929839d5cb5972883115040b11
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- K6iTifcJOwa/x51VhY2s4kll4FGlbtUpHeocoRblWBboOX9GhFu3ZR6eYs+wcG+OaHHxJpVQmBrZlDnvflxrBQ==