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
- 0f8c4fe94bec64e2b3d2d116bf011947b3d0c8d3e7a711c117cae3434b71bdb8
- request
- beb3358929d0eb12f88d328354096ace5ba204a54b584c1521b033a6b779bb91
- transaction
- 0b604ff4c061c2d261b1983ee37f766b1b003358d95596afbbd0fc3e2815200ccomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 14915
the chainentry 14915
- sealed to the entry before
- 181ef8797bd0591eea179dfba8380e9875178d5b63c7f8f049b1c50b61fa611b
- this leaf
- 599bfbfe4e758ac27bb778ef147d6a994e94e12aafbc0650d77101eeead9e1d2
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- Kb8py4mfUbZKgOTHLL9NfeKSBqo1ZnniR0HXnvh5D/YQY1Un1xj5e8y5zqsxw4NpRbomRjh+Chvu1xmMJt1aDg==