Accepting SEPA Credit payments

Available in: 🇪🇺 EU, 🇬🇧 UK
Supported currencies: EUR, GBP
Supported payer countries: Belgium, Ireland, Italy, Netherlands, UK

Overview

SEPA Credit Transfer (SCT) is a payment method used for cross-border and domestic Euro payments within the Single Euro Payments Area (SEPA) region. Both the sender and the recipient can be companies or individuals.

Use cases

SEPA Credit is one of the payment methods available for Monite payment links. Entities can use payment links to both send and receive SEPA Credit payments.

Receive invoice payments from counterparts

1. Entity uses the partner’s application to issue an invoice to a counterpart (client).
2. The application generates a payment link for this invoice. This payment link is automatically included in the invoice PDF and invoice email message sent to the counterpart. Entities can also share payment links with counterparts in any other way they prefer.
3. Counterpart navigates to the payment link. The payment page displays the payment amount, invoice details, and the entity bank account details.
4. To pay via SEPA Credit, the counterpart selects “Bank transfer” as the payment method and provides consent to withdraw the payment amount from their bank account.
5. Monite initiates the payment with the counterpart’s bank.
6. After the payment request is accepted by the counterpart’s bank, the funds are transferred via SEPA Credit to the entity bank account specified in the invoice.

Requirements

From an integration perspective, using SEPA Credit requires the following from Monite partners:

• Server side - to generate payment links, receive webhooks about the payment status, and (optionally) customize the look and feel of the payment page.
• Client side - you can use either Monite-hosted payment page (optionally masked with your own domain), or an embeddable Payment component.

Additionally:

• Both the sender (counterpart) and the recipient (entity) must be based in the EU or UK.
• If the recipient entity is based in the EU:
  • Payment currency must be EUR. For example, in case of invoice payment scenarios, the invoice currency must be EUR.
  • The entity’s default bank account must be in a country in the SEPA zone. See Entity bank accounts and Counterpart bank accounts to learn how to specify bank account details.
• If the recipient entity is based in the UK:
  • Payment currency must be GBP. For example, in case of invoice payment scenarios, the invoice currency must be GBP.
• Entity bank account must have the account holder name specified.

Scenario: Accept a SEPA Credit payment

This guide assumes an entity and its bank account have already been created.

1. Enable the SEPA Credit payment method for the entity

To check if SEPA Credit is already enabled for the entity, call GET /entities/{entity_id}/payment_methods. If sepa_credit is not present in the list of payment methods, call PUT /entities/{entity_id}/payment_methods to add it. For more information, see Enabling payment methods for an entity.

The example below assumes that card is a pre-existing payment method enabled for the entity, and we’re enabling the entity to both receive and send SEPA Credit payments.

1
curl -X PUT 'https://api.sandbox.monite.com/v1/entities/e4678...1f6/payment_methods' \
2
     -H 'X-Monite-Version: 2024-01-31' \
3
     -H 'Authorization: Bearer YOUR_PARTNER_TOKEN' \
4
     -H 'Content-Type: application/json' \
5
     -d '{
6
       "payment_methods_receive": [
7
         "card",
8
         "sepa_credit"
9
       ],
10
       "payment_methods_send": [
11
         "sepa_credit"
12
       ]
13
     }'

2. Create a payment link

A payment link is a URL that leads to a secure payment page where the payer (in this example, a counterpart) can specify their payment details and initiate the payment.

To generate a payment link, call POST /payment_links. In the request body, specify the recipient of the payment (in this example, an entity), the payment_methods to be displayed on the payment page, and other details. The required request fields vary based on whether or not the invoice being paid is stored in Monite. For more information, see Create a payment link.

1
curl -X POST 'https://api.sandbox.monite.com/v1/payment_links' \
2
     -H 'X-Monite-Version: 2024-01-31' \
3
     -H 'X-Monite-Entity-Id: ENTITY_ID' \
4
     -H 'Authorization: Bearer YOUR_PARTNER_TOKEN' \
5
     -H 'Content-Type: application/json' \
6
     -d '{
7
       "object": {
8
         "type": "receivable",
9
         "id": "RECEIVABLE_INVOICE_ID"
10
       }
11
       "recipient": {
12
         "type": "entity",
13
         "id": "ENTITY_ID"
14
       },
15
       "payment_methods": [
16
         "card",
17
         "sepa_credit",
18
       ],
19
       "return_url": "https://example.com/return-url"
20
     }'

A successful response returns a payment_page_url that can be shared with the payer.

1
{
2
  "id": "8babb691-3862-4676-97f4-d61b12284f25",
3
  ...
4
  "payment_intent": {
5
    "id": "e8dac9f8-e68c-4c8e-bcd3-b44cbb4f49d7",
6
    "updated_at": "2024-06-06T13:18:02.212807+00:00",
7
    "application_fee_amount": null,
8
    "object": null,
9
    "provider": null,
10
    "selected_payment_method": null,
11
    "status": "created"
12
  },
13
  "payment_intent_id": "e8dac9f8-e68c-4c8e-bcd3-b44cbb4f49d7",
14
  "payment_methods": [
15
    "card",
16
    "sepa_credit"
17
  ],
18
  "payment_page_url": "https://pay.sandbox.monite.com?data=eyJpZCI...",
19
  "payment_reference": "INV-00042",
20
  "recipient": {
21
    "id": "cd830c8d-df0f-4ebd-99b7-d290e3506004",
22
    "bank_accounts": [
23
      {
24
        "id": "dc1efc0a-aac1-43bd-878e-b17e4d4d3039",
25
        "account_holder_name": "Tobias Weingart",
26
        "bic": "DEUTDEFFXXX",
27
        "country": "DE",
28
        "currency": "EUR",
29
        "iban": "DE74500700100100000900",
30
        "is_default": true,
31
        ...
32
      }
33
    ],
34
    "name": "Acme GmbH",
35
    "type": "entity"
36
  },
37
  ...
38
  "status": "created"
39
}

A payment intent for tracking the payment is also automatically created and stored in the payment_intent field of the payment link. You can also access that payment intent directly by calling GET /payment_intents/{payment_intent_id}.

3. Share the payment link with the payer

After a payment link has been generated, the entity can share its URL (payment_page_url) with the payer (counterpart) using any way they prefer, for example, via email, via a website link or button, inside an app, or through other channels.

If the payment link was generated for an Accounts Receivable invoice created via Monite, the PDF invoice will include a QR code pointing to the payment link, and the invoice email notification will also include the payment link.

When the payer navigates to the payment link, they will see the payment page displaying information about the invoice and payment amount. The payer can select their preferred payment method and enter their payment information to initialize the payment.

4. Track the payment status

After the payer confirms the payment, the payment link status is changed to succeeded and the payment intent status is changed to processing. Monite triggers the following webhooks when the status of payment links and intents is changed:

• payment_link.status_updated
• payment_intent.status_updated

You can monitor the status of the payment intent to know when the payment has been settled or rejected. The ID of the payment intent is stored in the payment_intent_id field of the payment link and is also included in payment_intent.status_updated webhooks. For more information, see Track the payment intent.

Test SEPA Credit payments

See Testing payments for a list of test credentials that you can use with the sandbox version of the payment page to simulate user consent and test both successful and declined payments.