PHP应用支付场景下，如何用preg_match_all解析支付确认邮件数据？

Hey there! I’ve dealt with exactly this kind of scenario before—manual data extraction from payment confirmation emails when webhook POSTs fail is such a common pain point. Let’s get your preg_match_all working properly.

First, to give you targeted help, it’d be super useful if you could share two things:

• A redacted sample of the payment email text (hide sensitive info like full credit card numbers or personal details, but keep the structure intact—like how transaction IDs, amounts, and other key fields are formatted and positioned).
• Your current regex attempt and what’s going wrong (e.g., no matches at all, capturing the wrong data, or partial matches).

That said, here are some general tips that usually fix most email parsing issues with preg_match_all:

1. Anchor your regex to explicit field labels #

Payment emails almost always use consistent labels for key data (like "Transaction ID:", "Amount:", "Customer Email:"). Use these labels to target exactly what you need, instead of relying on vague patterns. For example:

// Match a transaction ID that looks like PAY-1234-ABC567
preg_match_all('/Transaction ID:\s*([A-Z0-9-]+)/i', $emailContent, $txnIdMatches);
$transactionId = $txnIdMatches[1][0] ?? null;

The \s* matches any number of spaces/tabs/newlines, and the i modifier makes the match case-insensitive (in case the email uses "transaction id:" instead of capitalized).

2. Handle newlines and messy whitespace #

Emails often have inconsistent line breaks or extra spaces. Use the s modifier in your regex to make . match newline characters if you need to match across lines. For example, if a field wraps to the next line:

// Match an amount that might be on the same line or next line as the label
preg_match_all('/Amount:\s*\$?([0-9]+\.[0-9]{2})/is', $emailContent, $amountMatches);
$amount = $amountMatches[1][0] ?? null;

3. Test and debug your matches #

After running preg_match_all, dump the matches array to see what’s being captured:

var_dump($matches);

This will show you if your capture groups are working, or if the regex is picking up unintended text.

Example Workflow #

Suppose your email looks like this:

Payment Confirmation

Thank you for your payment!
Transaction ID: TXN-7890-1234
Total Amount: $99.99
Customer: jane.doe@example.com

Here’s how you’d extract the key data:

$emailText = "Payment Confirmation\n\nThank you for your payment!\nTransaction ID: TXN-7890-1234\nTotal Amount: $99.99\nCustomer: jane.doe@example.com";

// Extract Transaction ID
preg_match_all('/Transaction ID:\s*([A-Z0-9-]+)/i', $emailText, $txnMatches);
$txnId = $txnMatches[1][0] ?? 'No match';

// Extract Amount
preg_match_all('/Total Amount:\s*\$?([0-9]+\.[0-9]{2})/i', $emailText, $amountMatches);
$amount = $amountMatches[1][0] ?? 'No match';

// Extract Customer Email
preg_match_all('/Customer:\s*([a-zA-Z0-9._%+-]+@[a-zA-Z0-9.-]+\.[a-zA-Z]{2,})/i', $emailText, $emailMatches);
$customerEmail = $emailMatches[1][0] ?? 'No match';

echo "Transaction ID: $txnId\nAmount: $$amount\nCustomer Email: $customerEmail";

This would output:

Transaction ID: TXN-7890-1234
Amount: $99.99
Customer Email: jane.doe@example.com

Once you share your actual email structure and regex attempts, we can tweak this to fit your specific case perfectly!

内容的提问来源于stack exchange，提问作者Greg Schmidt