credit_card (the client is not charged). If you want to make an authorization for a payment, you will need to send the capture as “false” within the card object, which is located inside the payment_method object.The unique identifier of the account. You find this information on Yuno's Dashboard (MAX 64; MIN 36).
The description of the payment (MAX 255; MIN 3).
The customer's country code (MAX 2; MIN 2; ISO 3166-1).
AR, BO, BR, CL, CO, CR, EC, SV, GT, HN, MX, NI, PA, PY, PE, US, UY The unique identifier of the customer's order (MAX 255; MIN 3).
Specifies customer object for payments.
Specifies the checkout object. This object is not mandatory for back to back payments. Required when workflow is defined as CHECKOUT or is not sent. not required for DIRECT payments.
Specifies the additional_data object. This object is not mandatory. However, if you send this information, the payment experience will be enhanced for your user.
Identification of the payment transaction defined by the merchant (MAX 255; MIN 3). Optional to complement the merchant_order_id.
Specifies the payment amount object, with the value and currency.
The payment workflow. Indicates whether the integration will use Yuno´s SDK or will be a back to back connection. CHECKOUT=Use Yuno SDK. DIRECT= Back to back integration with provider info for custom payment experience, REDIRECT= Back to back integration with provider redirection.
SDK_CHECKOUT, DIRECT, REDIRECT Specifies the order's tax object.
The payment method object.
Specifies a list of metadata objects. You can add up to 50 metadata objects.
The URL where to redirect the customer after the payment. Only required for DIRECT integrations that have a redirection (MAX 526; MIN 3).
201
"ebc54248-5bc7-4ab0-a74b-5567d09d8222"
"493e9374-510a-4201-9e09-de669d75f256"
"Test Cards"
"US"
"PENDING"
"AUTHORIZED"
"0000022"
"2024-06-06T20:46:31.000981Z"
"2024-06-06T20:46:31.475595Z"
"SDK_CHECKOUT"
""