Skip to main content
API

Paytia API - Braintree payment gateway - using the gateway_customer_control field to control the passed value in the gateway_customer_id field

The gateway_customer_control field lets you set your own Braintree customer IDs. Here are the valid values and the exact errors you'll get when one is wrong.

Error conditions

When using the Paytia API and connecting to the Braintree payment gateway, Paytia has added the ability for a developer to set their own Customer ID values as the Braintree Customer ID. 

API error message for control use cases:

Case 1: Gateway = Braintree, and gateway_customer_control is not within the valid values of '0' or '1'.

Error message returend: The value sent in the gateway_customer_control field is not supported. Please use a supported value {0,1}

Case 2: Gateway = Braintree, and gateway_customer_id is not provided, but a value of 1 is passed in gateway_customer_control.

Error message returned: A valid payment gateway customer ID value is required in the gateway_customer_id field when you are passing a '1' value in the gateway_customer_control field.

Case 3: Gateway = Braintree, and the value passed in the gateway_customer_id field already exists on the payment gateway.

Error message returned: The value you have passed in the gateway_customer_id field already exists on the payment gateway. If you want to create a new customer ID on the payment gateway with your own gateway customer ID value, please provide a different value in the gateway_customer_id field.

If you have any questions, please reach out to techsupport@paytia.com 

braintreegateway_customer_controlapi

More in API

Paytia API exception handling

The webhooks we send when something goes wrong mid-payment — the customer rejects the amount, the call drops, the card fails. Here's each case and what lands on your endpoint.

Paytia API services

Three API versions, depending on how much of the flow you want to control yourself. This is the overview of what each does and which one to pick.

Paytia development - embedded iframe events

If you embed our checkout rather than redirecting, we send postMessage events to your page so you can resize the frame and react to the outcome. These are separate from webhooks.

Paytia Proxy Gateway

The Proxy Gateway posts captured payment data to your own endpoint as JSON you define. Nothing is hard-coded, so you shape the payload to whatever's waiting on the other end.

Webhook request button

The Webhook Request button shows every webhook tied to one call or transaction, in order. It's the quickest way to see what your system was actually sent.

Webhooks sent from Paytia to API users for the payment capture IVR flow

What we post back at each stage of an IVR payment, and how your reference_id is carried through every webhook so you can match them up.

Still need help?

Our support team is here to help. Submit a ticket and we'll get back to you within one business day.

Submit a TicketBack to Knowledge Base