# Payment methods configuration

Starting from v0.16  paymemnt methods can be configured via UI under "Configuration management" -> "Purchase configuration" -> "Payment methods". 

Currently the following three payment methods are available: 

* “Bank Transfer” - user pays via bank transfer based on the invoice details configured by admin
* “Credit Card”  - user pays with his debit or credit card
* “Cryptocurrencies” - user pays with the listed tokens

All methods can be enabled only if they are properly configured and can be disabled at any moment.

<figure><img src="https://558541652-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FiTYqY7GQFlQO0s8Vbk2r%2Fuploads%2Fq2LaKzwPkzE8IegL3hEH%2Fimage.png?alt=media&#x26;token=21a23b6d-55ff-4060-8cb1-dc9d6d1d9702" alt=""><figcaption><p>"Configuration management" -> "Purchase configuration" -> "Payment methods"</p></figcaption></figure>

{% hint style="info" %}
Please note that

* there must be at least one configured and enabled payment method to switch on  "Featured asset" and/or "Asset purchase" featured
* if the "Featured asset" or/and "Asset purchase" features are switched on you can't disable all payment methods: at least one collection method must be configured and enabled
  {% endhint %}

### General characteristics for all payment methods

* Description of the method in all available languages for the portal which will be shown to user in the checkout flow in Payment method's tile details<br>

  <div><figure><img src="https://558541652-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FiTYqY7GQFlQO0s8Vbk2r%2Fuploads%2FkdENw7lekHm4ZeouPCGF%2Fimage.png?alt=media&#x26;token=536c795e-fb54-4470-a661-319d180eca2a" alt=""><figcaption><p>Description definition in the Configuration management</p></figcaption></figure> <figure><img src="https://558541652-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FiTYqY7GQFlQO0s8Vbk2r%2Fuploads%2FZ33f9JCXwveFc9J7Uj44%2Fimage.png?alt=media&#x26;token=b258722b-ca48-4c1c-b149-65549ddb6b00" alt=""><figcaption><p>Description is shown in the payment method's tile in user checkout flow</p></figcaption></figure></div>
* You can define KYC tier which users must have for each payment method to be able to use it during checkout process. By default Tier 0 is applied [Read more about KYC configurations](https://teos-docs.coreledger.net/white-label-portal/admin-user-guide/portal-configuration/features-configuration/kyc-checks)\
  ![](https://558541652-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FiTYqY7GQFlQO0s8Vbk2r%2Fuploads%2Fx07lnu0QpyTst3woDVoP%2Fimage.png?alt=media\&token=b48b53ab-c320-418b-8c2d-bfab2a2e3d45)
* You can define purchase amount limit, which the user must not exceed to use the corresponding payment method, when creating order. The limit is set in the portal currency, and has a number value. If the user exceeds the payment method limit, the payment method will not be available.

<div align="left"><figure><img src="https://558541652-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FiTYqY7GQFlQO0s8Vbk2r%2Fuploads%2FjvkdKKLDanDCWOTjhSFT%2Fimage.png?alt=media&#x26;token=d96dd718-16b6-45b2-b948-db60699f86e0" alt="" width="375"><figcaption><p>Purchase amount limit in Configuration management</p></figcaption></figure> <figure><img src="https://558541652-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FiTYqY7GQFlQO0s8Vbk2r%2Fuploads%2Fn1vd6sjzHpdqyL2aJY0q%2Fimage.png?alt=media&#x26;token=6346a0b5-7954-4285-a08e-e2b15a1acded" alt="" width="375"><figcaption><p>Purchase amount limits, displayed to the user</p></figcaption></figure></div>

### Additional characteristics of specific collection methods

#### Bank transfer payment method

Step 1. Configure bank transfer details

For the payment method “Bank Transfer” the bank details of the receiving account must be configured, they will be used in the invoice generated for the order. \
Descriptions for each field of the bank details are optional, in case you provide them, users will see them in info tooltip. Descriptions can be added in all languages available for the portal.&#x20;

<figure><img src="https://558541652-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FiTYqY7GQFlQO0s8Vbk2r%2Fuploads%2F1kZvY34VLjiXG3Sfhyqc%2Fimage.png?alt=media&#x26;token=7108e63e-0c99-4563-8970-6e5ea0bca114" alt=""><figcaption></figcaption></figure>

You can also add up to 3 additional bank ids (apart from SWIFT or BIC) in case your bank has some details apart from the regular ones. You have to provide name and value for each of them. And optionally you have possibility to add description in all languages available for the portal. We recommend to provide the description for such ids to make sure that users understand the purpose of them and make correct bank transfer.

<figure><img src="https://558541652-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FiTYqY7GQFlQO0s8Vbk2r%2Fuploads%2F5hOPCQpoqfyLEdaFflop%2Fimage.png?alt=media&#x26;token=d3dbc3d8-0ac7-428b-91fb-1400ace3e1e2" alt=""><figcaption></figcaption></figure>

You can also add details of intermediary bank in case you expect international payments and your bank has intermediary bank details for them. We recommend to add description for this section to explain to your users what it is. Optionally you can provide translations in all available languages.<br>

<figure><img src="https://558541652-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FiTYqY7GQFlQO0s8Vbk2r%2Fuploads%2FttNjc3AONuKqc0zJ5s8b%2Fimage.png?alt=media&#x26;token=636dd70c-3f78-4fed-aff1-0019aa51cd3d" alt=""><figcaption></figcaption></figure>

Step 2. Prepare the template for invoice details

Refer to [templates-for-purchase-details-and-invoice-details](https://teos-docs.coreledger.net/white-label-portal/admin-user-guide/portal-configuration/features-configuration/purchase-assets-and-featured-asset/templates-for-purchase-details-and-invoice-details "mention") to check how the template for invoice details must be configured. Send it to your CoreLedger manager to apply it in your portal

#### Credit card payment method

Step 1. Configure credit card payment parameters

Apart from the [#general-characteristics-for-all-payment-methods](#general-characteristics-for-all-payment-methods "mention") integration with cryptopayment provider must be configured to use this payment method.&#x20;

Currently integration with [Payrexx](https://www.payrexx.com/en/home/) is used for credit card payments.&#x20;

To use it productively you will have to provide your Payrexx account details:

* Payrexx account name (they also call it Instance Name in some documents)
* API secret&#x20;

Check [#bank-card-payment-provider-payrexx](https://teos-docs.coreledger.net/white-label-portal/admin-user-guide/how-to-get-api-keys-of-third-party-services#bank-card-payment-provider-payrexx "mention") to find integration parameters in your Payrexx account. Payrexx account configuration must be done separately according to Payrexx guidelines. Please, make sure that the portal currency is within the payment currencies configured for Payrexx.

<figure><img src="https://558541652-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FiTYqY7GQFlQO0s8Vbk2r%2Fuploads%2FKbGEQ189UiJHMBmS60QU%2Fimage.png?alt=media&#x26;token=55119cc1-11ec-4238-ac1a-52aebe3b5dc0" alt=""><figcaption></figcaption></figure>

For pilot project within Active Sandbox you can start without your own account, you are allowed to use CoreLedger test account. Discuss it with your CoreLedger manager.<br>

Step 2. Prepare the template for credit card purchase details

Purchase details based on this template are sent to the user when credit card is selected as a payment method. \
Refer to [templates-for-purchase-details-and-invoice-details](https://teos-docs.coreledger.net/white-label-portal/admin-user-guide/portal-configuration/features-configuration/purchase-assets-and-featured-asset/templates-for-purchase-details-and-invoice-details "mention") to check how the template must be configured. Send it to your CoreLedger manager to apply it in your portal.

#### Cryptocurrency payment method

Step 1. Configure credit card payment parameters

Apart from the [#general-characteristics-for-all-payment-methods](#general-characteristics-for-all-payment-methods "mention") integration with cryptopayment provider must be configured to use this payment method.&#x20;

Currently integration with [Coinify ](https://www.coinify.com/)is used for cryptocurrency payments.

To use it productively you will have to provide your Coinify account details:

* API key
* The environment, for which the API key is used (Sandbox or Production)

Check [#crypto-payment-provider-coinify](https://teos-docs.coreledger.net/white-label-portal/admin-user-guide/how-to-get-api-keys-of-third-party-services#crypto-payment-provider-coinify "mention") to find integration parameters in your Coinify account. Coinify account configuration must be done separately according to Coinify guidelines.&#x20;

<figure><img src="https://558541652-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FiTYqY7GQFlQO0s8Vbk2r%2Fuploads%2FUqOcbWg3ICmAZwawFs7o%2Fimage.png?alt=media&#x26;token=846eeb48-00f2-4ee0-af23-a41cb716f3b7" alt=""><figcaption></figcaption></figure>

For pilot project within Active Sandbox you can start without your own account, you are allowed to use CoreLedger test account. Discuss it with your CoreLedger manager.

Step 2. Prepare the template for cryptopayment purchase details

Purchase details based on this template are sent to the user when cryptopayment is selected as a payment method. \
Refer to [templates-for-purchase-details-and-invoice-details](https://teos-docs.coreledger.net/white-label-portal/admin-user-guide/portal-configuration/features-configuration/purchase-assets-and-featured-asset/templates-for-purchase-details-and-invoice-details "mention") to check how the template must be configured. Send it to your CoreLedger manager to apply it in your portal.