Identify incoming transactions using commercial or corporate card BINs by checking the payment_instrument_type and card_type fields in the Braintree transaction response
On transactions identified as commercial cards, include Level 2 fields in the transaction creation request: customer_reference_number (purchase order number) and tax_amount
Ensure tax_amount is accurate and non-zero; submitting zero tax on a commercial card transaction may disqualify it from Level 2 rates
Validate that your merchant category code (MCC) is eligible for Level 2 pricing with your acquiring bank; not all MCCs qualify
After settlement, pull transaction-level interchange data from your processor statement to verify the Level 2 rate was applied
Monitor the pass-through rate over time and alert if the Level 2 qualification rate drops, indicating a data quality issue
Known gotchas
Level 2 requirements differ between Visa and Mastercard; Visa requires tax amount and customer code, while Mastercard also requires tax indicator
The purchase order number field has a maximum length; truncate rather than omit if the PO number exceeds it, as omission drops you to Level 1
Consumer credit cards submitted with Level 2 data are ignored silently by the network; you only achieve lower rates on genuinely commercial card BINs
Give your agent this knowledge — and 200+ more routes
One MCP install gives any agent live access to the full route map, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp