Braintree Passthrough Fields
This page shows how to follow key payment data as it moves between Braintree and Verifone so you can match the same transaction in both systems. Product, engineering, finance, and ops teams can use this information to reconcile POS activity with Braintree reports and settlement data without manual guesswork.
The tables map specific fields (such as Order ID, Customer ID, Partner ID, amount, currency, and vault status) from Braintree's API responses to Verifone's response payloads, giving you a consistent set of identifiers for reporting, auditing, and troubleshooting.
from Verifone POS Cloud
Use this table to see how key fields in Verifone POS Cloud responses align with Braintree transaction data so you can carry the same identifiers across your in-store integration.
| POS Cloud | Associated Braintree Field |
|---|---|
salesData.invoiceNumber | Order ID |
paymentData.customer.identification.customerId | Customer ID |
paymentData.customer.identification.partner_id | Partner ID (BN Code) |
transaction.totalAmount.value | Amount |
transaction.totalAmount.currencyCode | Currency Code |
transaction.storedCredential.storedCredentialType.reuseTokenType =
"PAYPAL" | Vault Indicator |
from Verifone POS PSDK
Use this table to see how common PSDK payment fields map to Braintree values so your installed POS application can tag transactions with consistent order, customer, and vault metadata.
| PSDK | Associated Braintree Field |
|---|---|
Payment.setInvoiceId() | Order ID |
Payment.setCustomerId() | Customer ID |
Payment.setPartnerId() | Partner ID (BN Code) |
Payment.setRequestedAmounts(amountsTotal) | Amount |
Payment.setRequestedTokenParameters(TokenType::STORED_CREDENTIAL) | Vault Indicator |