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
- 78b83b67be82e0a1867fea59ee46643212a8211ba2ff6f7d14a1ad908b0cd0a9
- request
- e8a919344756174c03a3bfa59134e098308d1b4f6d51650ddc2be72bcec647f1
- transaction
- 68ec891cbcb425172adcb5929857130133d908df64c4aab8e7439cc2f8512986computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 73645
the chainentry 73645
- sealed to the entry before
- 4073c5a66fd3a8eab5e48dc5b927564cd6a347fbe28d1c22071690235863834d
- this leaf
- 5cb2f255d4ec686e0f02df2abc634413cda528961ee3ff50e8b0fb0f66da30ab
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- Rpwly/TYdEiq/S/05LwG8Zva8S34XBmQNX8UYZRrMWu65g+XZmEwSmS5dEOqYFI9e4YOEYat6V6kcfOP2mg6Cw==