Transaction
Transaction: Sale
See also the Transaction response object.
To create a transaction, you must include an amount and either a paymentMethodNonce, a paymentMethodToken, or a customerId. Passing a customerId is equivalent to passing the paymentMethodToken of the customer's default payment method.
Braintree offers products that manage risk and fraud related to each transaction. These products can only be leveraged if there is adequate data to support the capabilities. The required data can be easily added during the Braintree SDK or Graph QL. integration, and must be done prior using risk products. For additional guidance go to Premium Fraud Management Tools.
The following example creates a transaction using a paymentMethodNonce from a client and instructs that it should be submitted for settlement immediately using options.submitForSettlement. You can see more examples, including using a vaulted payment method, below the parameter reference.
- Java
TransactionRequest request = new TransactionRequest()
.amount(new BigDecimal("10.00"))
.paymentMethodNonce(nonceFromTheClient)
.deviceData(deviceDataFromTheClient)
.options()
.submitForSettlement(true)
.done();
Result<Transaction> result = gateway.transaction().sale(request);
if (result.isSuccess()) {
// See result.getTarget() for details
} else {
// Handle errors
}
Parameters
.amount(…)
BigDecimalThe billing amount of the request. This value must be greater than 0, and must match the currency format of the merchant account. Can only contain numbers and one decimal point (e.g. x.xx
). Can't be greater than the maximum allowed by the processor. Contact us for your specific limit.
Billing address information associated with a specific customer ID.
AVS rules are not applied when creating a transaction from a Vault record using a payment method token. We still submit the street address and postal code to the processor to run AVS checks. The transaction response includes processor AVS response codes.
.company(…)
string.countryCodeAlpha2(…)
stringThe ISO 3166-1 alpha-2 country code specified in an address. The gateway only accepts specific alpha-2 values.
PayPal transactions must use the alpha-2 format. See PayPal's country code documentation for details.
.countryCodeAlpha3(…)
stringThe ISO 3166-1 alpha-3 country code specified in an address. The gateway only accepts specific alpha-3 values.
.countryCodeNumeric(…)
stringThe ISO 3166-1 numeric country code specified in an address. The gateway only accepts specific numeric values.
.countryName(…)
stringThe country name specified in an address. We only accept specific country names.
.extendedAddress(…)
string.firstName(…)
string.countryCode(…)
string.nationalNumber(…)
string.lastName(…)
string.locality(…)
string.phoneNumber(…)
stringDeprecated.
We recommend using international_phone
. This functionality still exists in the gateway but is no longer documented. This parameter will be removed in the future.
.postalCode(…)
string.region(…)
string.streetAddress(…)
string.billingAddressId(…)
string.channel(…)
stringFor partners and shopping carts only
If you are a shopping cart provider or other Braintree partner, pass a string identifier for your service. For PayPal transactions, this maps to paypal.bn_code
.
Typically requires PCI SAQ D compliance
We recommend using paymentMethodNonce()
to avoid any PCI concerns with raw credit card data being present on your server.
A credit or debit payment method.
.cardholderName(…)
string.cvv(…)
stringA 3 or 4 digit card verification value assigned to credit cards.
To meet PCI guidelines, CVV will never be stored in the gateway. CVV is not required when creating a transaction from Vault tokens; CVV rules will be applied to transactions if and only if the CVV is supplied with the tokens.
CVV checking can also be done when you create or update the Vault record by using card verification.
.expirationDate(…)
stringMM/YY
or MM/YYYY
. May be used instead of expiration_month
and expiration_year
.MM
. May be used with expiration_year
, and instead of expiration_date
.YYYY
or YY
. May be used with expiration_month
, and instead of expiration_date
..cryptogram(…)
string.ecommerceIndicator(…)
string.tokenRequestorId(…)
string.number(…)
string.encryptedCardData(…)
string.keySerialNumber(…)
string.token(…)
stringAn alphanumeric value that references a specific payment method stored in your Vault. Must be less than or equal to 36 characters. If using a custom integration, you can specify what you want the token to be. If not specified, the gateway will generate one that can be accessed on the result. If using our Drop-in UI with a customer ID to vault payment methods, you can't specify your own token. Length and format of gateway-generated tokens and IDs may change at any time.
A collection of custom field/value pairs. Fields and values must be formatted as strings or integers. Maximum 255 characters. You must set up each custom field in the Control Panel prior to passing it with a request. Querying this value returns a collection of custom field values stored on the transaction object.
When storing a new customer in the Vault, you can use this object to specify the customer's details. Only use this parameter when creating a new customer with a new payment method. See the customer object for further details.
.company(…)
string.email(…)
string.fax(…)
string.firstName(…)
string.id(…)
string.countryCode(…)
string.nationalNumber(…)
string.lastName(…)
string.phone(…)
stringDeprecated.
We recommend using international_phone
. This functionality still exists in the gateway but is no longer documented. This parameter will be removed in the future.
.website(…)
string.customerId(…)
stringDynamic descriptors are not enabled on all accounts by default. If you receive a validation error of 92203
or if your dynamic descriptors are not displaying as expected, please contact us.
Dynamic descriptors are sent on a per-transaction basis and define what will appear on your customers' credit card statements for a specific purchase. The clearer the description of your product, the less likely customers will issue chargebacks due to confusion or non-recognition.
See the dynamic descriptor example for additional information.
.name(…)
stringThe value in the business name field of a customer's statement. The specific length/character requirements for this value depend on your processor. Contact us for assistance.
.phone(…)
string.url(…)
string.deviceData(…)
stringCustomer device information. Required in the following cases:
- When using Premium Fraud Management Tools
- When creating one-time Vaulted PayPal transactions
- When creating Venmo transactions
This value will contain a Device Session ID as the unique identifier for a customer device. For Fraud Protection, PayPal, and Venmo transactions, this value will also include a PayPal Correlation ID. Provide the full string received from the Braintree client SDK.
.deviceSessionId(…)
stringDeprecated.
We recommend including the device session ID within deviceData()
. This functionality still exists in the gateway but is no longer documented. It will remove this param/attr when the corresponding gateway code is removed.
.discountAmount(…)
BigDecimalA Level 3 field that specifies the discount amount that was included in the total transaction amount. It can't be negative, and it does not add to the total transaction amount. This Braintree line-item field is not used by PayPal.
.exchangeRateQuoteId(…)
string.status(…)
stringThe option indicates the vaulted status of the externally vaulted payment method. Accepted values:
vaulted
= Indicates the payment method is already stored on behalf of the customer.will_vault
= Indicates the payment method is intended to be vaulted upon successful processing of the transaction.
.fraudMerchantId(…)
stringfraud_merchant_id
with your requests ensures that we will route them to your specific Kount account for evaluation.The line items for this transaction. It can include up to 249 line items. If your merchant account has been configured for Level 3 processing this field will be passed to the processor on your behalf.
.commodityCode(…)
string.description(…)
string.discountAmount(…)
BigDecimal.kind(…)
stringIndicates whether the line item is a debit (sale) or credit (refund) to the customer. Accepted values:
"debit"
"credit"
.name(…)
string.productCode(…)
string.quantity(…)
BigDecimal.totalAmount(…)
BigDecimal.unitAmount(…)
BigDecimal.unitOfMeasure(…)
string.unitTaxAmount(…)
BigDecimal.upcCode(…)
string.upcType(…)
stringUPC type for the item. If specified, you must also provide the UPC code. Accepted values:
"UPC-A"
"UPC-B"
"UPC-C"
"UPC-D"
"UPC-E"
"UPC-2"
"UPC-5"
.url(…)
string.merchantAccountId(…)
stringThe merchant account ID used to create a transaction. Currency is also determined by merchant account ID. If no merchant account ID is specified, we will use your default merchant account.
.accountType(…)
stringSpecifies which account type the transaction should be processed with. This will need to be set up even if the account_type
parameter was passed in the corresponding 3D Secure call as it will not carry over.
Accepted account types are:
credit
(default)debit
.holdInEscrow(…)
booleanFor Braintree Marketplace merchants only. This value specifies whether a transaction is held in escrow. See Escrow for more detail.
.customField(…)
string.description(…)
string.customerEmail(…)
string.customerFirstName(…)
string.customerLastName(…)
stringPrevents the transaction from being evaluated as part of Premium Fraud Management Tools checks. Use with caution – once you've skipped checks for a transaction, it is not possible to run them retroactively.
.skipAvs(…)
booleanSkip AVS checks for the transaction. Will result in a processor response code of B
for avsPostalCodeResponseCode and avsStreetAddressResponseCode, and nil
for avsErrorResponseCode. Use with caution – once you've skipped checks for a transaction, it is not possible to run them retroactively.
.skipCvv(…)
booleanSkip CVV checks for the transaction. Will result in a processor response code of B
for cvvResponseCode. Use with caution – once you've skipped checks for a transaction, it is not possible to run them retroactively.
.storeInVault(…)
boolean.storeInVaultOnSuccess(…)
booleanThe option that determines whether the shipping address information provided with the transaction should be associated with the customer ID specified. When passed, the payment method will always be stored in the Vault.
If there is already a shipping address associated with the customer, this parameter will not replace the existing information; an additional address will be stored instead. You can associate up to 50 addresses with a single customer ID.
.submitForSettlement(…)
boolean.required(…)
booleanSpecify whether to require 3D Secure verification to succeed before creating a transaction. Defaults to true for transactions sent through 3D Secure verification but to false for transactions not sent through 3D Secure verification. For more information, see 3D Secure advanced server-side options.
.profileId(…)
string.orderId(…)
string.paymentMethodNonce(…)
stringOne-time-use reference to payment information provided by your customer, such as a credit card or PayPal account. Can be passed instead of a paymentMethodToken parameter.
.paymentMethodToken(…)
stringAn alphanumeric value that references a specific payment method stored in your Vault. Must be less than or equal to 36 characters. If using a custom integration, you can specify what you want the token to be. If not specified, the gateway will generate one that can be accessed on the result. If using our Drop-in UI with a customer ID to vault payment methods, you can't specify your own token. Length and format of gateway-generated tokens and IDs may change at any time.
.purchaseOrderNumber(…)
stringA Level 2 field that can be used to pass a purchase order identification value of up to 12 ASCII characters for AIB and 17 ASCII characters for all other processors.
.recurring(…)
booleanDeprecated.
We recommend using transactionSource()
with a value of recurring
.
A value indicating whether the transaction is being passed with a recurring ecommerce indicator (ECI) flag. If passed, the amount submitted for settlement must exactly match the authorized amount.
AVS and CVV rules do not apply to recurring payments.
Customer device information, which is sent directly to supported processors for fraud analysis. These fields are automatically populated if using Premium Fraud Management Tools. Currently only available when processing American Express via Amex Direct. Contact us with any questions.
.customerBrowser(…)
stringUser-Agent
header provided by the customer's browser, which gives information about the browser. Maximum 255 characters..customerIp(…)
string.scaExemption(…)
stringSpecifies the Secure Customer Authentication exemption that this transaction will be claiming.
Accepted values:
low_value
secure_corporate
trusted_beneficiary
.serviceFeeAmount(…)
BigDecimalThe portion of a sub-merchant's transaction revenue that is routed to the master merchant account. If set, this value must be greater than or equal to 0, must match the appropriate currency format, and can't exceed the transaction amount.
Available to Braintree Marketplace merchants. See charging a service fee and holding funds in escrow on Braintree Marketplace transactions.
.company(…)
string.countryCodeAlpha2(…)
stringThe ISO 3166-1 alpha-2 country code specified in an address. The gateway only accepts specific alpha-2 values.
.countryCodeAlpha3(…)
stringThe ISO 3166-1 alpha-3 country code specified in an address. The gateway only accepts specific alpha-3 values.
.countryCodeNumeric(…)
stringThe ISO 3166-1 numeric country code specified in an address. The gateway only accepts specific numeric values.
.countryName(…)
stringThe country name specified in an address. We only accept specific country names.
.extendedAddress(…)
string.firstName(…)
string.countryCode(…)
string.nationalNumber(…)
string.lastName(…)
string.locality(…)
string.phoneNumber(…)
stringDeprecated.
We recommend using international_phone
. This functionality still exists in the gateway but is no longer documented. This parameter will be removed in the future.
.postalCode(…)
string.region(…)
stringThe shipping method used for the shipping address. Possible values:
- sameDay
- expedited
- priority
- ground
- electronicDelivery
- shipToStore
- pickupInStore
.streetAddress(…)
string.shippingAddressId(…)
string.shippingAmount(…)
BigDecimalA Level 3 field that specifies the shipping cost on the entire transaction. It can't be negative, and it does not add to the total transaction amount.
.shippingTaxAmount(…)
BigDecimalA Level 3 field that specifies the amount of tax that was charged on the shipping amount. The value can't be negative, and in most cases, it must be greater than zero if the shipping amount is greater than zero. It does not add to the total transaction amount.
.shipsFromPostalCode(…)
stringA Level 3 field that specifies the postal code of the shipping location.
.surchargeAmount(…)
BigDecimal.taxAmount(…)
BigDecimalA Level 2 field that specifies the amount of tax that was included in the total transaction amount. The value can't be negative, and in most cases, it must be greater than zero in order to qualify for lower interchange rates. It does not add to the total transaction amount.
.taxExempt(…)
booleanA Level 2 field that indicates whether or not the transaction should be considered eligible for tax exemption. This does not affect the total transaction amount.
Results of a merchant-performed 3D Secure authentication. You will only need to use these fields if you've performed your own integration with a 3D Secure MPI provider (e.g. Cardinal Centinel). Otherwise, Braintree's SDKs handle this for you in our standard 3D Secure integration.
.cavv(…)
stringCardholder authentication verification value or CAVV. The main encrypted message issuers and card networks use to verify authentication has occurred. Mastercard uses an AVV message and American Express uses an AEVV message, each of which should also be passed in the cavv parameter.
.dsTransactionId(…)
stringTransaction identifier resulting from 3D Secure 2 authentication. This field must be supplied for Mastercard Identity Check.
.eciFlag(…)
stringThe value of the electronic commerce indicator (ECI) flag, which indicates the outcome of the 3DS authentication.
Accepted values for Mastercard:
00
= Failed or not attempted01
= Attempted02
= Success04
= Data-Only (Applies to limited processors)
Accepted values for all other card brands:
07
= Failed or not attempted06
= Attempted05
= Success
.threeDSecureVersion(…)
stringThe version of 3D Secure authentication used for the transaction. Required
on Visa and Mastercard authentications. Must be composed of digits separated
by periods (e.g. 1.0.2
).
.xid(…)
stringTransaction identifier resulting from 3D Secure authentication. Uniquely identifies the transaction and sometimes required in the authorization message. Must be base64-encoded. This field will no longer be used in 3D Secure 2 authentications.
.transactionSource(…)
stringSpecifies the source of the transaction. The value passed depends on whether the transaction is initiated by the merchant or the customer. If the transaction is an ecommerce transaction initiated by the customer, no value is passed.
Accepted values for merchant-initiated transactions:
recurring
= Transactions for subsequent recurring payments (e.g. subscriptions with a fixed amount on a predefined schedule).unscheduled
= Transactions for unscheduled payments that are not recurring on a predefined schedule or amount (e.g. balance top-up). Formerlymerchant
.installment
= Transactions for subsequent installment payments. (e.g. when the customer makes a single large purchase and wants to make payments over time).
Accepted values for customer-initiated transactions:
recurring_first
= Transactions that represent the first in a series of recurring payments or subscription.moto
= Transactions that are initiated by the customer via the merchant by mail or telephone.installment_first
= Transactions that represent the first in a series of installment payments.estimated
= Transactions that support subsequent incremental authorization.
Note: installment
and installment_first
may only be available in certain regions. If installment transactions are not supported in your region, the transaction will automatically be categorized as recurring
.
Learn more about the Visa Stored Credential Framework in our blog.
Examples
Full example
Here is an example of passing in everything a typical merchant might use.
Some parameters are mutually exclusive, so we'll show those in separate examples. If there is anything you want to store with the transaction details that we don't have a field for, you can always use custom fields.
Collect device data from the client and include the deviceDataFromTheClient in the transaction.
- Java
TransactionRequest request = new TransactionRequest()
.amount(new BigDecimal("10.00"))
.orderId("order id")
.merchantAccountId("a_merchant_account_id")
.paymentMethodNonce(nonceFromTheClient)
.deviceData(deviceDataFromTheClient)
.customer()
.firstName("Drew")
.lastName("Smith")
.company("Braintree")
.phone("312-555-1234")
.fax("312-555-1235")
.website("http://www.example.com")
.email("drew@example.com")
.done()
.billingAddress()
.firstName("Paul")
.lastName("Smith")
.company("Braintree")
.streetAddress("1 E Main St")
.extendedAddress("Suite 403")
.locality("Chicago")
.region("IL")
.postalCode("60622")
.countryCodeAlpha2("US")
.done()
.shippingAddress()
.firstName("Jen")
.lastName("Smith")
.company("Braintree")
.streetAddress("1 E 1st St")
.extendedAddress("Suite 403")
.locality("Bartlett")
.region("IL")
.postalCode("60103")
.countryCodeAlpha2("US")
.done()
.options()
.submitForSettlement(true)
.done();
Result<Transaction> result = gateway.transaction().sale(request);
If all the parameters are valid, a transaction will be created with a status of submitted_for_settlement and success? will return true.
- Java
result.isSuccess();
// true
Transaction transaction = result.getTarget();
transaction.getType();
// Transaction.Type.CREDIT
transaction.getStatus();
// Transaction.Status.SUBMITTED_FOR_SETTLEMENT
Storing in Vault
When creating a transaction, you can also store the payment method in your Vault.
Existing customer with new payment method
To associate this transaction's payment method with an existing customer, pass a customerId along with options.storeInVault or options.storeInVaultOnSuccess as true.
- Java
TransactionRequest request = new TransactionRequest()
.amount(new BigDecimal("10.00"))
.paymentMethodNonce(nonceFromTheClient)
.customerId("the_customer_id")
.options()
.storeInVaultOnSuccess(true)
.done();
Result<Transaction> result = gateway.transaction().sale(request);
New customer with new payment method
To store a payment method for a new customer, set options.storeInVault or options.storeInVaultOnSuccess to true on your transaction. You can optionally specify customer parameters for your new customer, as well:
- Java
TransactionRequest request = new TransactionRequest()
.amount(new BigDecimal("10.00"))
.paymentMethodNonce(nonceFromTheClient)
.customer()
.id("a_customer_id")
.done()
.options()
.storeInVaultOnSuccess(true)
.done();
Result<Transaction> result = gateway.transaction().sale(request);
Using a vaulted payment method
You can create a transaction using a payment method stored in the Vault by passing a paymentMethodToken:
- Java
TransactionRequest request = new TransactionRequest()
.paymentMethodToken("the_token")
.amount(new BigDecimal("10.00"));
Result<Transaction> result = gateway.transaction().sale(request);
Or use customerId, which will use the customer's default payment method:
- Java
TransactionRequest request = new TransactionRequest()
.customerId("the_customer_id")
.amount(new BigDecimal("10.00"));
Result<Transaction> result = gateway.transaction().sale(request);
Using a CVV-only nonce
To transact with a CVV-only nonce, use both a nonce representing the CVV and a paymentMethodToken representing the vaulted payment method.
To collect a CVV-only nonce, use the client SDKs to tokenize only the CVV property. See an example in our Hosted Fields FAQ.
- Java
TransactionRequest request = new TransactionRequest()
.paymentMethodToken("the_token")
.paymentMethodNonce(cvvOnlyNonceFromClient)
.amount(new BigDecimal("10.00"));
Result<Transaction> result = gateway.transaction().sale(request);
Specify merchant account ID
To specify which merchant account to use, pass the merchantAccountId when creating the transaction.
- Java
TransactionRequest request = new TransactionRequest()
.amount(new BigDecimal("100.00"))
.merchantAccountId("your_merchant_account")
.paymentMethodNonce(nonceFromTheClient);
Result<Transaction> result = gateway.transaction().sale(request);
If you don't specify the merchant account to use to process a transaction, Braintree will process it using your default merchant account.
Contact us if you would like to change which merchant account is default.
Using stored addresses
You can use addresses stored on a customer by passing the address's ID. This works for both the shipping address and billing address.
- Java
TransactionRequest request = new TransactionRequest()
.customerId("the_customer_id")
.amount(new BigDecimal("10.00"))
.billingAddressId("AA")
.shippingAddressId("AB");
Result<Transaction> result = gateway.transaction().sale(request);
Custom fields
Whatever you configure as the API name for your custom fields will be used when setting them on the transaction. Here is an example of setting custom fields with API names of custom_field_one
and custom_field_two
.
- Java
TransactionRequest request = new TransactionRequest()
.amount(new BigDecimal("100.00"))
.paymentMethodNonce("nonce-from-the-cleint")
.customField("custom_field_one", "value one")
.customField("custom_field_two", "value two");
Result<Transaction> result = gateway.transaction().sale(request);
Transaction transaction = result.getTarget();
transaction.getCustomFields();
// {custom_field_one=value one, custom_field_two=value two}
Dynamic descriptors
Dynamic descriptors are typically composed of a name and phone number or URL. The name must include the business name, followed by a product name or identifier, separated by an asterisk (*). Depending on the type of transaction you're creating, the length/character limits may differ from those outlined above. For example, you can only specify up to 18 characters for dynamic descriptor names on Braintree Marketplace transactions. See below for details on Venmo, PayPal, and Braintree Marketplace dynamic descriptors.
Your processor may also restrict which descriptor values you can pass; certain processors allow you to pass URLs instead of phone numbers, while others accept only phone numbers or only names. If your processor supports URLs and you send both a phone number and URL, we will only pass the URL to the processor. Contact us for more information on your processor's specific requirements.
- Java
TransactionRequest request = new TransactionRequest()
.amount(new BigDecimal("100.00"))
.paymentMethodNonce(nonceFromTheClient)
.descriptor()
.name("company*my product")
.phone("3125551212")
.url("company.com")
.done();
Result<Transaction> result = gateway.transaction().sale(request);
Transaction transaction = result.getTarget();
transaction.getDescriptor().getName();
// "company*my product"
transaction.getDescriptor().getPhone();
// "3125551212"
Venmo
Venmo only supports the dynamic descriptor name
. Its format allows alpha-numeric characters and +-.
(space included); any other characters will result in the dynamic descriptor name not being included in the full descriptor sent to the processor.
The full descriptor submitted to the processor is structured as follows:
- The default prefix of
(Two whitespaces).VENMO *
- The
Business Name
submitted in the Venmo application form. - The
Dynamic Descriptor Name
submitted in the transaction.sale() or transaction.submit_for_settlement() call.
An example of a full descriptor with a valid dynamic descriptor name is:
VENMO *AStore O-1234, where AStore
is the Business Name
and O-1234
is the Dynamic Descriptor Name
.
If the dynamic descriptor name contains invalid characters, e.g. 0#1234, the entire dynamic descriptor name will be ignored.
PayPal
The PayPal dynamic descriptor is limited to a total of 22 characters and includes the following elements:
- The default prefix of
PAYPAL *
- Your PayPal hard descriptor*
- The product portion of your
name
(learn more below)
*Depending on your PayPal account setup, the PayPal hard descriptor may not be included in the dynamic descriptor. You can update the hard descriptor value from your PayPal console.
The name must meet the following guidelines:
- Must include your registered Doing Business As (DBA) name, followed by an asterisk and a product description
- The DBA portion must be 3, 7 or 12 characters long - this portion will be dropped from your dynamic descriptor
The payment information displayed to a customer in their PayPal account overview does not contain the dynamic descriptor. The information displayed there is data the merchant has configured with PayPal directly (e.g. business name, email address, business contact details).
Braintree Marketplace
The only dynamic descriptor value we will pass for Braintree Marketplace transactions is the name you specify. We will not send any dynamic phone or url values to the processor, but we will pass the phone from the hard descriptor on your master merchant account.
The dynamic descriptor name can only contain the ASCII characters a-z, A-Z, the numbers 0-9, and the characters .-+
and spaces (it can't contain special characters like Ñ
, ü
, and é
). The maximum length is 18 characters; we will truncate any longer strings. The descriptor we pass to the processor will start with "BT *"
, followed by the name you specify.
- If the specified name is 12 characters or fewer, the descriptor we pass to the processor will end with a randomly generated 6-character string (e.g.
123abc
) which identifies the sub-merchant:
BT *MYDESCRIPTOR123abc
- If the specified name is 13 characters or greater, the descriptor we pass to the processor will not end with a randomly generated 6-character string:
BT *MYDESCRIPTORISLONG
Hold a Braintree Marketplace transaction in escrow on creation
Upon creating a Braintree Marketplace transaction, you can specify that its funds should be held in escrow. These funds can then be released at your discretion. By default, funds are not held in escrow.
- Java
TransactionRequest request = new TransactionRequest()
.amount(new BigDecimal("100.00"))
.merchantAccountId("blue_ladders_store")
.paymentMethodNonce(nonceFromTheClient)
.options()
.submitForSettlement()
.holdInEscrow()
.done()
.serviceFeeAmount(new BigDecimal("10.00"))
.done();
Result<Transaction> result = gateway.transaction().sale(request);