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
- 347234b1791e6a8f6dca9be6be2aac0051699849a94b0d93ead3997b20f9989a
- request
- 49974f093c81938a24c63949846bd59aa9fa504db1716970d79678144d8cfbdc
- transaction
- f903178b890d4ead638b484be0671bae98924d200d0baf3dc7c814b0beff6929computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 27500
the chainentry 27500
- sealed to the entry before
- 534a66f62b6bd33673582f2bd72921122fbf21dec972b37782d4dea23b3e748d
- this leaf
- 9bb9f3759188aaee585c3dd7c50914defcd4123fbff3f5083a241fec694802e9
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 1mlbVM9w45NO2mBxXbV1Wa2gwnIQx05J5i3zecEpLmB8KaEOPztCKqmaosfLZjXeEJDmGazTj+U360K+2E8HAw==