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
- b3a047a30136150298ab0d2f7440e95003772671d3d9d11abbcb090177346ae1
- request
- b6d43821e2bcd780bcc756f26a89b797c27d4d9eff6a6cc10e1ad9cb1397bad4
- transaction
- 14112dbbfd57c67c698ede26b5758f30a1a2e5db166e49b5e1ded69606d005b1computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 35940
the chainentry 35940
- sealed to the entry before
- fe1093edb295e0f80ec7e06336423f0592c8909d4fe03871b723d4859381e8dc
- this leaf
- ea5efc93e8764000b091490a9e85ef054f346655c7d9719c5dfad824eb344b00
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 1ILu0TgmLs+YzBjzwKjEiBDs2l75S1a5eP4XkZ/CPJF98ktCAysShHbhzZN0HBuZETZpEld2VO6C5w1NZNlKBA==