--- title: Payments slug: ref/payments docTags: createdAt: 2023-12-06T11:09:50.665Z --- In order to accept credit card or other payments, you need to peform a few steps: 1. Activate one or more payment gateways 2. Set up payment methods 3. Set up payment scenarios *** # 1. Activate a payment gateway A payment gateway is a service that authorizes online payments and processes them securely with a user’s merchant account. Funds received are transferred directly from the payment gateway to you, Ticketmatic is not involved in that process. There are a large number of payment gateways active on the market and each have their own advantages. It is up to you to select a payment gateway that best suits your needs. Ticketmatic can technically support all common payment gateways, provided they meet the minimum quality requirements. :::hint{type="info"} Contact you Ticketmatic account manager to help you selecting your payment gateway. ::: When you have activated the payment gateway, you are ready to set up your payment methods. *** # 2. Set up payment methods A payment method specifies how an actual payment is made, and it is linked to a specific payment gateway. Payment methods are managed in the Settings app. Click the button below to go to the Payment methods module: :::CtaButton{label="Go to payment methods" externalHref="https://apps.ticketmatic.com/#!/settings/paymentmethods" openInNewTab="true"} ::: ## Adding a payment method :::ExpandableHeading ### Stripe 1. Click the `Add` button 2. Fill in a name for the payment method and select type `Stripe` 3. Fill in the `secret key` and `publishable key` for your Stripe account. These can be found in your Stripe acount under Your account -> Account settings -> API Keys. ::: :::ExpandableHeading ### PayPal 1. Click the `Add` button 2. Fill in a name for the payment method and select type `PayPal` 3. Fill in the `Client ID` and `Client Secret` for the REST API of your PayPal account. ::: :::ExpandableHeading ### Mollie 1. Click the `Add` button 2. Fill in a name for the payment method and select type `Mollie` 3. Fill in the `API key` for your Mollie account 4. Fill in the Mollie payment method to be used ::: :::ExpandableHeading ### Internal 1. Click the `Add` button 2. Fill in a name for the payment method and select type `Internal` ::: *** # 3. Set up payment scenarios A payment scenario defines how a customer will pay for an order. For each sales channel you define the payment scenarios that are available. Payment scenarios are either `immediate` or `deferred`. - An order with a payment scenario of type `immediate` must be paid **before** the order can be confirmed. You will need to link an appropriate payment method. The payment will be processed by the payment gateway that is linked to the payment method. - An order with a payment scenario of type `deferred` can be confirmed without an immediate payment and can be paid later. Ticketmatic supports 5 kind op payment scenario's: | Payment scenario | Type | Description | | -------------------- | --------- | ------------------------------------------------------------------------------------------------------------------------------------------------- | | Immediate | Immediate | For example online credit card payment | | Bank transfer | Deferred | The payment must be executed by making a bank transfer to a specified account | | Deferred online | Deferred | After confirmation, the buyer will receive a mail with a link to carry out this payment. Payment can be carried out online using this link | | Deferred other | Deferred | The payment will be executed after confirmation of the order | | Mollie bank transfer | Deferred | (Only available when payment gateway Mollie is active) The payment must be executed by making a bank transfer to a bank account managed by Mollie | Payment scenarios are managed in the Settings app. Click the button below to go to the Payment scenarios module: :::CtaButton{label="Go to payment scenarios" externalHref="https://apps.ticketmatic.com/#!/settings/paymentscenarios" openInNewTab="true"} ::: ## Adding a payment scenario :::ExpandableHeading ### Immediate A typical example of this kind of payment scenario is Online credit card (for online orders) or a Cash payment (for box office orders). **Parameters:** - **Payment methods**: You have to specify the payment methods that can be used when selecting this payment scenario. ::: :::ExpandableHeading ### Bank transfer Payment is done by performing a regular bank transfer to a regular bank account. **Parameters:** - **Bank account number**: IBAN code of the bank account - **Bank account bic**: BIC code of the bank account - **Bank account beneficiary**: Beneficiary for the bank account - **Payment instructions**: Specify a mail template that will be sent out containing the payment instruction. Specific placeholders can be used in this mail to display bank account number, amount to pay, reference and expiry date. ::: :::ExpandableHeading ### Deferred online The payment must be executed online, but this can be done later. The customer will receive a mail with a link to carry out this payment. This can be used for example when handling phone orders: the custom can pass his order by phone, and will receive then a mail containing a link to execute the payment. **Parameters:** - **Payment methods**: Specify one or more online payment methods that are allowed - **Payment instructions**: Specify a mail template that will be sent out containing the payment instruction and a link to perform to actual online payment ::: :::ExpandableHeading ### Deferred other In this case, the payment can be executed later and the order can be confirmed without payment. **Parameters:** - **Payment instructions**: Specify a mail template that will be sent out containing the payment instruction ::: :::ExpandableHeading ### Mollie bank transfer Payment is done by performing a regular bank transfer to Mollie. Once the bank transfer is received by Mollie, the payment status of the order in Ticketmatic will be automatically updated. Mollie will also handle exceptions like customers paying the wrong amount. The bank transfer should be performed by the customer before the expiration date that is calculated from the setting `Expire after`. When this date is passed, Mollie will cancel the request. If the payment is received after this moment, Mollie will automatically refund it to the customer. Due to the way banks process bank transfers, the expiration date cannot be enforced exactly. Mollie will allow 1 working day extra to receive the payment. So in an rare cases, the payment might still arrive 3 days after the theoretical expiration date. Mollie will notify Ticketmatic when a payment request is cancelled, and the Ticketmatic order is updated to reflect this status change. Depending on your settings, the order will be marked expired, or will be deleted. In any case, Ticketmatic will expire orders with expiration date more than 7 days in the past and that are unpaid. **Parameters:** - **Payment methods**: Specify a payment method that links to a Mollie bank transfer method - **Payment instructions**: Specify a mail template that will be sent out containing the payment instruction. Specific placeholders can be used in this mail to display bank account number, amount to pay, reference and expiry date. ::: ## Order expiry for deferred payment scenarios For order with a deferred payment scenario, you can configure overdue and expiry parameters to define how long the order can stay unpaid before considering the order as overdue or expired. You can automatically send out reminder mails or even cancelling the order automatically when it expires. When you activate expiry for a payment scenario, it will automatically be made unavailable if the date of the first event in an order is too close. If for example you define expiry after 10 days, the payment scenario will only be available for new orders when the first event in the order is at least 11 days in the future. This way, you can be sure that either the payment is received or that the order is cancelled on time. :::hint{type="info"} The expiry date is recalculated each time you update the payment scenario for an order, and we use the current date as starting point for calculating expiry. ::: ## Fee An order fee can defined for a payment scenario: this fee will automatically be added to the order when the payment scenario is selected. ## Availability A payment scenario is available for one or more sales channels. A custom script can further refine when the payment scenario is available. [More info on creating availability scripts](docId:1Pi6ql7ecEm9BRYn4dBvv)