Date Updated: 5/3/2019← Back to Bolt P2PE API Changelog
This release includes the following updates:
Bolt has been updated with improved logic for handling timed out transactions. When Bolt does not receive an authorization response from the CardPointe Gateway, Bolt uses the CardPointe Gateway API inquireByOrderid endpoint to check on the status of the authorization attempt. If no status is returned, Bolt sends three voidByOrderID requests to void the transaction. If enough time remains in Bolt's request sequence, Bolt retries the authorization. Otherwise, Bolt returns an authorization failed error, and the request must be resent. See Handling Timeouts in the Bolt Developer Guides for more information.
- Support for refunds - You can now specify a negative amount value to initiate a negative authorization (forced credit). Note that the merchant account must be enabled to process forced credit transactions.
- Ability to create profiles - You can now use the data in the request to create a payment profile. If you set the createProfile parameter to true, Bolt initiates a request to the CardPoint Gateway profile endpoint to create a secure stored payment profile. See the CardPointe Gateway API Profile endpoint description for detailed information.
- Default orderid values - To support the improved timeout handling logic, Bolt now automatically generates a unique order ID in the format <HSN-timestamp> if the orderId parameter is not included in the request.