Braintree

Discover more about the Braintree connector and how to use it on the Digibee Integration Platform.

Important information:

  • This documentation is currently available only in English but will soon be translated into Portuguese.

  • The content is under revision and may change. We appreciate your understanding as we work to improve the documentation.

Process payments using Braintree Payments.

Parameters

Take a look at the configuration options for the component. Parameters supported by Double Braces expressions are marked with (DB).

Required Tab

ParameterDescriptionDefault valueData type

Dynamic Account

When activated, the connector will use the account dynamically. When deactivated, it’ll use the account statically.

false

boolean

Account Name (DB)

The name of the account that is generated dynamically via the Store Account connector.

string

Account

Sets the account to be used by the connector.

N/A

Account

Api Name

What kind of operation to perform

string

Method Name

What sub operation to use for the selected operation

string

Fail On Error

If true will stop pipeline with an error, if false will let the pipeline continue but the output will show a property success with value false

false

boolean

Optional Tab

ParameterDescriptionDefault valueData type

Environment (DB)

The environment Either SANDBOX or PRODUCTION

N/A

string

In Body (DB)

Sets the name of a parameter to be passed in the exchange In Body

N/A

string

Merchant Id (DB)

The merchant id provided by Braintree.

N/A

string

HTTP Read Timeout

Set read timeout for http calls.

N/A

number

HTTP Log Level

Set logging level for http calls, see java.util.logging.Level

string

HTTP Log Name (DB)

Set log category to use to log http calls.

Braintree

string

Log Handler Enabled

Sets whether to enable the BraintreeLogHandler. It may be desirable to set this to ‘false’ where an existing JUL - SLF4J logger bridge is on the classpath. This option can also be configured globally on the BraintreeComponent.

true

boolean

Successful executions should output at least a property "success": true

Last updated