Background
Payment Methods in the BigCommerce integration are pulled from BC down to iPaaS.com. Payment methods often need to sync up to other systems so be sure to cover this during implementation.
Payment Methods can be initialized from BigCommerce TO iPaaS.com.
Matching
No matching scheme is implemented for BC Payment Methods.
Payment Method Custom Fields
No default custom fields are created for BC Payment Methods.
BigCommerce Custom Fields
Custom fields are not supported on Payment Methods in BC so therefore none can be brought into iPaaS.com or be sent to BC.
iPaaS.com Custom Fields
Custom fields are not added by default for Payment Methods in this integration.
Payment Types TO iPaaS.com
Webhooks (External)
Payment methods only come TO iPaaS.com via initialization so there is no need to turn on a webhook to pull them into iPaaS.com. Should one be added in the future it can be added via initialization.
Data Mapping
BC Payment Method To IPaaS
Maps fields from the payment type in BC to Payment Methods in iPaaS.com.