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
- ab85730ab7e0e42b4c27b3236ddd28b2faa682def9087e9cd2cd0551be88b05f
- request
- 83e69ab3139a91e7513b0872acb551952617aeb07113a6941491f727503ad524
- transaction
- b1309a9426fdc077f3c18f2c1dca54af0b607aa25301a9912503c65bd47765b4computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 70144
the chainentry 70144
- sealed to the entry before
- 6ddba8d3bf68f4fa60956f465cd896c0b33ace7b6923c72796d98f5276d8f80c
- this leaf
- e9fdc556f2323edc99ac6f702cd1ed1916d87ef4018996b18a55c62095ffd4d0
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- ilMMHL/Ha39uiVpqM+2ApC87jOCoAfpAj7IE3C4hU5RMfHkWyLKZ2EYWDx6i95op3B0Y8G0KrHSm6cw2osHnDg==