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
- 030edb5f90d5ec1f05b87de3608ae93147a7dc2cff3e5a9cbb306f9891d83b06
- request
- c725e409b1ea3a6d306483bdfa0d42329b398be25494e55b452905f3ca37bfc2
- transaction
- edea29fd3aec5b4ebd8fd622e36df4cf8da5f9b0b7c5c9bc9d42817da1731f86computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 47028
the chainentry 47028
- sealed to the entry before
- 72a4b44a65af03d4b453f7e0dbf43f409d29d83b0f46ebf0f23279ca45f2e2b7
- this leaf
- 8e631879505a597b7eb67bbea59e533c84a74f63e01ea5c944d4111025257c45
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- orZvhjW2JGSgiCG5N2ZdjnuqU60HBriFGzsjcxwBvfA1kZ0g2VhXdGfLGXhnuApq0hZ2xeSiQISqo6G5iZP4CA==