1 # org.fsf.payment.trustcommerce
3 This extension allows CiviCRM users to use TrustCommerce.
5 The extension is licensed under [AGPL-3.0](LICENSE.txt).
12 ## Installation (Web UI)
14 This extension has not yet been published for installation via the web UI.
18 Intall the module in your custom extensions directory. The name of the top
19 level directory unpacked by the tarball should be changed to
20 `org.fsf.payment.trustcommerce`.
22 You will need to add rows to `civicrm_payment_processor_type` in your database.
24 | id | name | title | description | is_active | is_default | user_name_label | password_label | signature_label | subject_label | class_name | url_site_default | url_api_default | url_recur_default | url_button_default | url_site_test_default | url_api_test_default | url_recur_test_default | url_button_test_default | billing_mode | is_recur | payment_type | payment_instrument_id |
25 | 19 | TrustCommerce | TrustCommerce (org.fsf.payment.trustcommerce) | TrustCommerce Payment Processor | 1 | NULL | Vendor ID | Password | | | Payment_TrustCommerce | https://vault.trustcommerce.com/trans/ | | https://vault.trustcommerce.com/trans/ | | https://vault.trustcommerce.com/trans/ | https://vault.trustcommerce.com/trans/ | https://vault.trustcommerce.com/trans/ | | 1 | 1 | 1 | 1 |
29 Go to Administer -> System Settings -> Payment Processors and add The
34 There are no hooks for installation and uninstallation of plugin, so tables
35 need to be updated manually.
37 If the class names in the `civicrm_payment_processor_type` or
38 `civicrm_payment_processor` tables are incorrect, then they need to be changed
39 to `Payment_TrustCommerce`.