Looking at the AuthorizeDotNet connector code, I need to understand how to access: 1.…
- User
Looking at the AuthorizeDotNet connector code, I need to understand how to access:
- Email information from payment requests (should be available in customer data)
- Invoice number information (likely should come from metadata or payment request)
Let me examine the PaymentRequest and router_data structures to understand where this data would be accessible.
Assistant
I'll help you examine the AuthorizeDotNet connector code to understand how email and invoice number information are accessed from payment requests. Let me start by looking at the relevant files.
First, let's find the AuthorizeDotNet connector files:
Other models, same or similar prompt
Responses were produced in different, uncontrolled contexts (system prompts, settings, prior turns). This is not a benchmark.
Identical first prompt
claude-haiku-4-5-20251001Compare side by side →
claude-haiku-4-5-20251001Compare side by side →
claude-haiku-4-5-20251001Compare side by side →
claude-haiku-4-5-20251001Compare side by side →
claude-haiku-4-5-20251001Compare side by side →
claude-haiku-4-5-20251001Compare side by side →
claude-haiku-4-5-20251001Compare side by side →
claude-haiku-4-5-20251001Compare side by side →
claude-haiku-4-5-20251001Compare side by side →
claude-haiku-4-5-20251001Compare side by side →
claude-haiku-4-5-20251001Compare side by side →
claude-haiku-4-5-20251001Compare side by side →