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
- d98fbc5a790351b53facfa923310ca6c3d629c731217a8ee7fb8f6cd9e972850
- request
- 9e5556c9d46b8a85bf1600da5f3379c1460deaa0eebfd6e3d7db0e3178597900
- transaction
- 661cd24fdec3ec3d50deb35680fbfb9c7200e632ff1fee5dbd98df034156899ecomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 45125
the chainentry 45125
- sealed to the entry before
- bca22a8572e1f5fcce6a0eeaa62d6c7a78c5c7e59e9b8f179bb78da06ee9433a
- this leaf
- 233a0c4ef978c865201baba6b8eeeb3ccbfc0fbe2fe1cf4478e6c3d6c638e67f
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- o54xPVQrWjK3nWiUHoCN2M61+iZbE4+q/scl35BYCAmtkKgVjSk4WByAsAJ3ec44VUFpzD3tg6GaQht0JaRvBw==