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
- 40cab0a20a202d56944aaa3546ab358343ce02ac682955a511e2533e8fdb65d1
- request
- 1d6745db3ca60cabe36e541aa8dc8b2c65e2fe0193f7c0901376d13a3591027b
- transaction
- 125622840b98c994c6e8e10b8f5a75bcc33fd13e3e3c104cea7486b8f3390ff4computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 20511
the chainentry 20511
- sealed to the entry before
- 873ec8746376689e4e0e880dfc2f0c5ecd50f6918cb835f055bf4d6943a9b3f5
- this leaf
- c6a7407ebbf4919ff1f3023133fabeb6653ac16a9b544f285e3397b15bcd83ec
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- s2NqdWl4etl07Qb6bAOotdUKM6fsH8uIHaLlCNSc6L3yW9bcKZQPs9yh3wh+geai5hvOQlmoKqRc0UDnG411BQ==