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
- 69f7b15e138c8ee0551d772fb926c31e7ea41a674ce1963357cd0c34cdb96201
- request
- e9ef89cc8963eba536f719ed7937c6318f0800cda5a0a3f49f937ba83d726958
- transaction
- 3cab88d039dd3cccb4b8c65bc074fe041759295f7a0630ff8189a91d6e6db659computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 28004
the chainentry 28004
- sealed to the entry before
- 08aaefa9a7359552c2a52cf87f06ed6daeb5d906daf23f2d15cf64a7975e1fb9
- this leaf
- 5200daa5f0b3956fdca9361eabc44676a6e36e5fa89823ebf01713290d196c0e
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- FUEy3dXi2jQhbwYJiTtNCk5qyGvblTUiXJ+qfSRdx0lGyfNnNN1SYcuMDuQYHJa5rf5z5gXzjrfnT8kZJk+hDQ==