Payment options

The payment option object and the allowed CRUD operations on the related resource endpoint

Payment options can be associated with an order to extend the information we send to the payment gateway at the moment of the payment creation. That information must be provided using the data object in a valid JSON format. The data key/value pairs will be merged into the root of the payload sent to the gateway and used to properly create the payment itself. The provided payment options won't override information we already send to the gateway, only new attributes will be added to the payload.

Payment options are payment source type-specific and may vary based on the different payment gateway. Make sure to carefully read the gateway documentation so that you can build the data JSON object properly, otherwise the gateway might return an error.

For security reasons, payment options can be managed using integration API credentials only.

Remember to associate the payment options to the order before the payment source creation to ensure they are properly injected into the payload we send to the gateway. Similarly, if for any reason the payment source associated with the order should change (e.g. changing the gateway type), make sure to remove the old payment options association or update them to the ones requested by the new payment source type, otherwise the gateway might not accept the payment.

Last updated