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
- 50ea53f3d9b06aa89d610a739a6d3c5dcfcc6d7110c8041bc4842655bb748c30
- request
- 7a7e7428fcc9bf0269e06ae069ff32b0ec7062e02458f9fdac6e15cf4d418d32
- transaction
- 0959599a92b1d62f754c333b8627b6345b5c8f8f3827a152f23860d25c613a87computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 61203
the chainentry 61203
- sealed to the entry before
- beeaaa6cca00b05c15669964527b73198c77df4a0fb6994784b0d9e8e03a51d6
- this leaf
- c5c902e37e40b72bef89f3907d434b9791417ecc69eab08e00971844a1b2b0c4
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- akuOEoJ01lBVOYbWU6Zc1XcTxxfV1N7k2mqgYc5qDLQKi9El0I9DIZOZCktY0SSV3jph7rXJWqZgYq7n0URjCQ==