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
- 62a5be7a20caf9807827e3449fd57cdf15ce7551ad2afed7811d1f5c038e5281
- request
- 3aa173b074f618de34b153439fe1b2d1a213a0da2618e418a33a020a198fc142
- transaction
- e8798d030bb12165103938d432c834fb0840bb77747be1056f630d84b5964e18computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 29619
the chainentry 29619
- sealed to the entry before
- 9e430c2b914c392be4a1cd04e1eab36e61b6c7a2dd04ae5959777be42dbe0c6a
- this leaf
- 58872e41d75ae4320cf8e76ece6b2be1be15af3d63228b727b6908ff17ec4233
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- +9P56mjPk5rtzZzzttgYjkuY3M39ox2+xd70HrZ3LoPi9Y2Ur/mKtTi/z8si3GPSU83PSoCQk/otUDbMeIRnAA==