Integration and Testing

[zstern]

Hello,

Should 

GetTransactionListForCustomerController

return records in the sandbox if transactions were run for the customerProfileId? 

[ElaineM]

Hi zstern, 

Get Customer Profile Transaction List Description: 

Use this method to retrieve transactions for a specific customer profile or customer payment profile. The function will return data for up to 1000 of the most recent transactions in a single request. Paging options can be sent to limit the result set or to retrieve additional transactions beyond the 1000 transaction limit. If no customer payment profile is supplied then this function will return transactions for all customer payment profiles associated with the specified customer profile. This allows you to retrieve all transactions for that customer regardless of card type (such as Visa or Mastercard) or payment type (such as credit card or bank account). You can add the sorting and paging options shown below to customize the result set.

Please make sure that you have transactions processing in live mode that are being recorded in the Merchant Interface and can be found. If you are running transactions in test mode this will not be the case. 

Regards, 

Elaine

[zstern]

If I create a transaction and then create a customer profile using that transaction id, will that transaction be returned when I call GetTransactionListForCustomerController?

[ElaineM]

Hi zstern, 

No, it will not. Only transactions processed after the profile is created will return here. 

Regards, 

Elaine

[heonii99]

No, it will not. Only transactions processed after the profile is created will return here. 

[emmathornber]

Malware authors are constantly working to respond to the newest, most sophisticated threat detection. Some primary sandbox evasion techniques include.

• Detecting the Sandbox: Sandbox environments look slightly different than an end user’s real system. If malware detects a sandbox, it can either terminate immediately or stall execution of harmful activities.
• Exploiting Sandbox Gaps and Weaknesses: As sophisticated as a particular sandbox might be, malware authors can often find and exploit its weak points. One example is using obscure file formats or large file sizes that the sandbox can’t process. Or, if the sandbox’s monitoring method is circumvented, the sandbox gains a “blind spot” where malicious code can be deployed.
• Incorporating Context-Aware Triggers: cokernutx -aware malware works by exploiting weaknesses of the automated sandbox technology. For example, what are sometimes referred to as “logic bombs” can delay code detonation for a specified period of time or until triggers occur that typically only happen in an end user’s system—like system reboots or keyboard and mouse interactions.