Based on the user's request, I need to understand how to pass the connector request…
- User
Based on the user's request, I need to understand how to pass the connector request reference ID in payment requests to Braintree. Looking at the existing Braintree connector implementation in hyperswitch, I need to examine how to properly add orderId to payment requests. Let me check if there are any hints about the orderId field in the Braintree API.
Assistant
I'll help you understand how to pass the connector request reference ID in payment requests to Braintree in hyperswitch. Let me first examine the existing Braintree connector implementation to see how orderId or similar fields are handled.
First, let me search for the Braintree connector files in the codebase:
Assistant
Now let me examine the Braintree connector implementation to understand how it currently handles payment requests:
Assistant
Now let me check the transformers module to understand how payment requests are structured and where orderId might be handled:
Assistant
Let me search for how the orderId or reference ID is handled in the Braintree connector to understand if there's already any support for it:
Assistant
Let me also check for the Braintree API documentation to better understand how orderId should be passed:
Assistant
Let me also search for how the connector request reference ID is typically handled in other connectors to understand the expected pattern:
Assistant
Let me check some other connectors that handle orderId to understand the pattern:
Assistant
Let me check the broader patterns in other connector implementations for reference:
Assistant
(no content)
Assistant
Now let me examine the Braintree API documentation to understand the orderId field. Let me also look for the payment request data structure to see if there are any references to connector request ID or reference:
Assistant
Let me examine the main Braintree connector structure again, looking specifically for the payment input types:
Assistant
Let me check the API request structures that are being sent to Braintree to understand the schema:
Assistant
Let me also check how the payments request is actually constructed for authorization in the Braintree connector. Now I need to look at what kind of information is available in the router data to understand where we could add orderId.
Let me look at what data is accessible in the payments request structure:
Assistant
Let me look at the payment request data structure in the router:
Assistant
(no content)
Assistant
(no content)
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-sonnet-4-5-20250929Compare side by side →
claude-sonnet-4-5-20250929Compare side by side →
claude-sonnet-4-5-20250929Compare side by side →
claude-sonnet-4-5-20250929Compare side by side →
claude-sonnet-4-5-20250929Compare side by side →
claude-sonnet-4-5-20250929Compare side by side →
claude-sonnet-4-5-20250929Compare side by side →
claude-sonnet-4-5-20250929Compare side by side →
claude-sonnet-4-5-20250929Compare side by side →
claude-sonnet-4-5-20250929Compare side by side →
claude-sonnet-4-5-20250929Compare side by side →