Skip to main content
Related API: This extension modifies the Perform Payment Action operation.
This action occurs after a certain interaction is performed on a payment. It runs after both the embedded.commerce.payments.action.before and the embedded.commerce.payments.performPaymentInteraction actions. The main difference between these three actions is the methods each has access to and whether they occur before or after the payment interaction. The relevant payment interactions that this action responds to are:
  • AuthAndCapture
  • Authorize
  • Capture
  • Create
  • Credit
  • Decline
  • RequestCheck
  • Rollback
  • Void
Action TypeEmbedded
Full Action IDembedded.commerce.payments.action.after
Runs multiple custom functions?Yes

JavaScript File Structure

Action files share the following basic structure:
When you code the custom function for an action, you have access to two arguments: callback—This argument follows the established JavaScript callback pattern: it takes an error as the first argument (or null if there is no error) and a result as the second argument (if required). context—This argument provides the function access to relevant objects and methods that interface with Kibo.

Context: Payment

The methods and objects documented here are available to this action through the use of the context argument. Microservice Operation This action corresponds to the microservice that performs payment actions.

Get

get.payment

Returns the payment transaction. Example:
Response:
For information about the properties in the response, refer to the REST API Help.

get.paymentAction

Returns a primitive list of strings naming the available payment actions. Example:
Response:

Exec

exec.setActionAmount

Set a requested payment amount for the transaction. Example:
Response:
Returns a payment action. For information about the properties in the response, refer to the REST API Help.

exec.setPaymentData

Set custom payment data (usually billing information associated with a billing service that might only send an auth token). Example:
Response:
For information about the properties in the response, refer to the REST API Help.

exec.removePaymentData

Remove custom payment data from a payment. Example:
Response:
For information about the properties in the response, refer to the REST API Help.

exec.setActionPreAuthFlag

Enable pre-authorization for an order payment. Pre-authorization authorizes a small dollar amount (e.g. $1) in order to check the authorization response for errors (incorrect CVV, etc.) before the full amount is authorized. This feature provides a cleaner method for authorizing large-value orders. To enable this feature, contact your Kibo representative. At this moment, Cybersource is the only payment gateway that supports this feature. Example:
Response:
For information about the properties in the response, refer to the REST API Help.

exec.setBillingInfo

Set the billing info object for a payment. Example:
Response:
For information about the properties in the response, refer to the REST API Help.

Context Objects Available to All Actions

apiContext

Accesses tenant information. Example:

configuration

Receives a JSON response that contains information about the configuration data set in the Action Management JSON editor. Example: