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
- b23931419ae2be7236724d42ce7dde95a6a2d3e2987e06d3c6a48b3f65c05030
- request
- 67771004a98effee06f345bbfcc646dcaf2527cc2a909cb4cf3cd9a9af63eceb
- transaction
- 6ad733dfb516483052812249756caf9c5b0b6f42a9f893005611620a1283983dcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 30686
the chainentry 30686
- sealed to the entry before
- b592b57029478d20fc53977f0ebca29cca6bd6698ec2f7b05c68e2ec2265cfd4
- this leaf
- 65a8bf429e9ec46637146974fa364d90940310e15bbdbe5f2b8a4423e92589f5
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- ekN9fxO7ASlNalcV2+isuojpNDKx7W490prw+3OLsZbWX3ucyzHvU+Nc91eXjEVUGrjaNqjOgT7GBI7zBgrpAw==