Sepa Debit Charge
Use the Charge API to initiate a new Sepa Debit Payment. Confirmation of the Charge creates the Charge object used to request payment.
Note: SEPA Direct Debit is a delayed notification payment method, which means that funds are not immediately available after payment. A payment typically takes 5 business days to arrive in your account.
Create A Charge
We recommend using our recommended payments integrations to perform the tokenization process client-side. This ensures that no sensitive card data touches your server and allows your integration to operate in a PCI-compliant way. By using client-side tokenization, you benefit from the following:
- You need to tokenize the charge object before sending it to Axxonpay's Charge API.
- You can refer to the tokenization page to handle the tokenization aspect by either using the Client Tokenization method or the Token API.
POST /v1/process/sepa-payment
const axios = require('axios');
const data = {
// Add your request body data here
token: tokenized,
};
const headers = {
signature: 'sig_<Your-Signature>',
authorization: 'key_<Your-Key>'
};
// Make the POST request
const response = await axios.post('https://<axxonpay-url-gateway>/v1/process/sepa-payment', data, { headers });
Parameters
Parameter | Required/Optional | Type | Description |
---|---|---|---|
amount | REQUIRED | Number | Amount intended to be collected by this Charge. A positive integer representing how much to charge in the smallest currency unit (e.g., 100 cents to charge $1.00 or 100 to charge ¥100, a zero-decimal currency). The minimum amount is $0.50 US or equivalent in charge currency. The amount value supports up to eight digits (e.g., a value of 99999999 for a USD charge of $999,999.99). |
currency | REQUIRED | String | Three-letter ISO currency code, in lowercase. Must be a supported currency. |
customer_id | OPTIONAL | String | ID of the Customer this Charge belongs to, if one exists. Payment methods attached to other Customers cannot be used with this Charge. If present in combination with setup_future_usage, this Charge's payment method will be attached to the Customer after the Charge has been confirmed and any required actions from the user are complete. |
checkout_id | OPTIONAL | String | ID of the Payment this Charge belongs to. |
description | OPTIONAL | String | An arbitrary string attached to the object. Often useful for displaying to users. |
iban | REQUIRED | String | Number of the IBAN Bank Account used for the charge. |
line1 | REQUIRED | String | First line of the address associated with the card used for the charge. |
line2 | REQUIRED | String | Second line of the address associated with the card used for the charge. |
postal_code | REQUIRED | String | Postal code of the address associated with the card used for the charge. |
city | REQUIRED | String | City of the address associated with the card used for the charge. |
country | REQUIRED | String | Country of the address associated with the card used for the charge. |
REQUIRED | String | Email address of the customer associated with the charge. | |
name | REQUIRED | String | Name of the customer associated with the charge. |
state | REQUIRED | String | State of the address associated with the card used for the charge. |
remote_ip | REQUIRED | String | IP address of the customer making the charge. |
Testing Sepa Direct Debit
You can mimic a successful or failed charge by first creating a token with one of the following test IBAN account numbers. Use the charge request to create a test charge that is either successful or failed.
ACCOUNT NUMBER | DESCRIPTION |
---|---|
AT611904300234573201 | The charge status transitions from pending to succeeded. |
AT861904300235473202 | The charge status transitions from pending to failed. |
AT591904300235473203 | The charge status transitions from pending to succeeded, but a dispute is immediately created. |