Overriding Token Exchange

Usually, a client provides a temporary token (nonce) that is exchanged with a Payment Gateway Provider for a long term token (the payment token). In some situations, the token exchange is performed before Payment Service processing. In this situation, the Payment Service accepts and stores the token. You can configure the Payment Service to store the token for all messages received by the Payment Gateway Provider or on a per-message basis.

Apply to All Messages

Set the bypassTokenExchange property to true in the payment-service.yaml file so that all payment request messages with an operation of Add Payment Method encode and return the token without exchanging it with the Payment Gateway Provider: 
payment:
  gateway:
    paymentGatewayProvider:
      configs:
        default:
          bypassTokenExchange=true

Where paymentGatewayProvider is the name of a Payment Gateway Provider (such as Braintree).

Apply to Current Message Only

To override the token exchange on a per-message basis, use the MtxChargeMethodOverrideFlagsExtension SubMan API. For example: 
{"$":"MtxChargeMethodOverrideFlagsExtension","ExchangeToken":false}

For more information about the MtxChargeMethodOverrideFlagsExtension SubMan API, see MATRIXX Subscriber Management API.