You can typically find alerts by searching for the last 4 digits of the card number within your payment processor. However, this would not often be the case as banks would often tokenize the card number, which makes it challenging to locate the corresponding transaction for the alert. In such cases, you instead use the other following details which are provided in the alert:

• Transaction date within +/- 1 day
• Amount
• Issuer
• Card Scheme
• Descriptor

This situation typically arises in Apple Pay-Goldman Sachs transactions. For instance, if a merchant is using Stripe and has received an alert containing the following details but is unable to locate the transaction using only the last 4 digits of the card number, they may utilize the other details provided, similar to the photo below.

Sample alert details:

• Last 4 digits: 1234
• Transaction date: July 2, 2024
• Amount: $49 USD
• Card Scheme: Mastercard
• Issuer: Goldman Sachs

After applying the relevant filters, you should review each transaction to check for any matches with the alert.

When using Link Payments on Stripe, you might find it difficult to access the card details. However, if you are utilizing Stripe Radar for Fraud Teams, you can view the card information by clicking on the risk evaluation next to the payment method. In the screenshot below, you can see that the clickable link is labeled "Normal" under the Risk Evaluation. Once you click on it, a pop-up will appear, allowing you to scroll down and access the card information.

If you're a Stripe user and there are multiple matches or transactions with no card details, we recommend turning on our Descriptor Append Feature. This will help you easily find the exact transaction of difficult-to-find alerts, such as tokenized card types like Apple Pay or Stripe Link, which may occasionally omit details. This will save time and ensure that almost every alert is appropriately matched, thereby reducing the chance of any unmatched alerts slipping through, and resulting in a lower dispute rate.

To set up, simply choose a base string and we will attach an 8-digit alphanumeric code to it. This code is generated from the Stripe invoice string and serves as the unique identifier for your alerts. It remains constant for each individual customer and should be recognizable to them if you are using Stripe email receipts, as it matches the exact string on their invoice.

Before turning on the descriptor, please inform us if you will be adding a descriptor that is not currently enrolled with us. We need to ensure that the correct string is set up with the data providers. You are limited to a total of 22 characters for a billing descriptor, so the prefix must be a maximum of 16 characters. Additionally, we recommend adding a space after the descriptor, for example: "descriptor. " We can provide the following suggestions:

[insert descriptor] XXXXXXXX = 21 characters

[insert descriptor] #XXXXXXXX = 22 characters