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
- df9061be545f811c341658585254e143c80f7af98aead28d407b243d5e6c8a1e
- request
- 12461943cb977f45946e133a861ff9ef8388675b86b6fe540dee44978fe99bb1
- transaction
- 4f8b83d7793e33278a9cf679feaf31336bf5e1c7d33854c14b1264e29b6f3cb3computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 13870
the chainentry 13870
- sealed to the entry before
- 8bf42717a5c9d9fea85e5465748361fa71fd5118aba626f81e07c0ac7ddc2a21
- this leaf
- 43004f77f59f23eb0c787c1d9ae6518af0368fd6cc96d3b8adf70384f9f05b45
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- rwGO2Qa8zRo3eGgE/k2rVCqnkMdnP5UHpY+Uljotwb1LDT+R2R+gk/4E8cz2bBiJGY9arhW2CtfMNinjVqmMBw==