CSV Import Columns
Exact column names, aliases, and requirements for each CSV import type.
Download the CSV Import Templates spreadsheet for ready-to-use column headers for each import type.
Lead Import
Service: LeadImportService
Required Columns
| Column | Description |
|---|---|
Name |
Customer full name |
Email |
Customer email address |
IBAN |
IBAN (strict identifier) |
BIC |
BIC/SWIFT code |
Optional Columns
| Column | Description |
|---|---|
Address1 |
Street address line 1 |
Address2 |
Street address line 2 |
City |
City |
State |
State/Province |
Country |
ISO 3166-1 alpha-2 country code |
Zip |
Postal/ZIP code |
MandateDate |
SEPA mandate signing date |
Phone |
Phone number |
AssignedGateways |
Comma-separated gateway identifiers |
Column Aliases
Case-insensitive. Alternative headers that map to canonical column names.
| Alias | Maps To |
|---|---|
name, full name, fullname, customer name |
Name |
email, email address, e-mail |
Email |
iban, iban / account no, account |
IBAN |
address1, address 1, address line 1 |
Address1 |
address2, address 2, address line 2 |
Address2 |
city |
City |
state |
State |
country |
Country |
zip, zip code, postal code, postcode |
Zip |
mandatedate, mandate date, mandate_date |
MandateDate |
phone, phone number, telephone, tel, mobile |
Phone |
bic, bic/swift, swift, swift code, bank code |
BIC |
assignedgateways, assigned gateways, assigned_gateways, gateways, gateway, terminal, terminals, mid |
AssignedGateways |
Order Import
Service: OrderImportService
Order import supports two modes per row: commerce mode and direct mode. There are no globally required columns; validation is per-row based on mode.
Commerce Mode Columns
Required when a row uses campaign-based pricing:
| Column | Description |
|---|---|
Campaign ID |
Campaign UUID |
Offer ID |
Offer UUID |
Direct Mode Columns
Required when a row does not reference a campaign:
| Column | Description |
|---|---|
Amount |
Payment amount |
Currency |
Currency code |
GatewayID |
PaymentGateway UUID |
BillingType |
One of: ONE_OFF, RECURRING, TRIAL_RECURRING |
Lead Identifier Columns
At least one must be present per row:
| Column | Description |
|---|---|
Lead ID |
Lead UUID |
IBAN |
IBAN to match existing lead |
Optional Columns
| Column | Description |
|---|---|
BillingFrequency |
WEEKLY, BIWEEKLY, MONTHLY, QUARTERLY, SEMIANNUALLY, YEARLY |
TrialIntervalUnit |
day, week, month |
TrialPeriod |
Trial period duration (integer) |
TrialPrice |
Trial price (decimal) |
WebhookProfileID |
WebhookProfile UUID for explicit webhook routing |
Inline Lead Creation
If a row includes Name, Email, and BIC columns alongside IBAN, the system creates a new lead inline (or resolves an existing one). Lead column aliases from the Lead Import service are supported.
Column Aliases (Pricing)
| Alias | Maps To |
|---|---|
amount, price |
Amount |
currency |
Currency |
billingtype, billing_type, billing type |
BillingType |
billingfrequency, billing_frequency, billing frequency |
BillingFrequency |
trialintervalunit, trial_interval_unit, trial interval unit |
TrialIntervalUnit |
trialperiod, trial_period, trial period |
TrialPeriod |
trialprice, trial_price, trial price |
TrialPrice |
Column Aliases (Gateway)
| Alias | Maps To |
|---|---|
gatewayid, gateway_id, gateway id |
GatewayID |
paymentgatewayid, payment_gateway_id, payment gateway id |
GatewayID |
Column Aliases (Webhook)
| Alias | Maps To |
|---|---|
webhookprofileid, webhook_profile_id, webhook profile id |
WebhookProfileID |
Transaction Import
Service: TransactionImportService
Required columns are adapter-specific. They are loaded at runtime from the adapter's YAML configuration (required_columns key under transactions).
EMP Required Columns
| Column |
|---|
Unique ID |
IBAN / Account No |
DateTime (UTC) |
Merchant |
BIC / SWIFT code |
Finxp Required Columns
| Column |
|---|
END TO END ID |
MERCHANT |
CUSTOMER BIC |
CUSTOMER IBAN |
STATUS |
TRANSACTION TYPE NAME |
AMOUNT |
IMPORTED DATE |
TRANSACTION INFORMATION |
Novalnet Required Columns
| Column |
|---|
TID |
IBAN |
PaymentDate |
MerchantName |
BIC |
Column mappings (mapping CSV headers to internal model fields) are defined in each adapter's YAML config. See Adapter Configuration.
Chargeback Import
Service: ChargebackImportService
Required columns are adapter-specific. They are loaded at runtime from the adapter's YAML configuration (required_columns key under chargebacks).
EMP Required Columns
| Column |
|---|
Unique ID |
Merchant Transaction ID |
Finxp Required Columns
| Column |
|---|
End to end id |
Transaction Information |
Initiated amount |
Currency |
Status |
Chargeback date |
Initiated date |
Novalnet Required Columns
| Column |
|---|
ChargebackTID |
ParentTID |
Column mappings are defined in each adapter's YAML config. See Adapter Configuration.
Cancellation Import
Service: CancellationImportService
Required Columns
None strictly required. Validation is flexible: at least one identifier column must be present per row.
Identifier Columns
At least one must be present per row:
| Column | Lookup Order |
|---|---|
merchant_transaction_id |
Highest priority. Resolves Transaction, then Subscription. |
iban |
Resolves Lead, then finds actionable Subscriptions. |
email |
Resolves Lead, then finds actionable Subscriptions. |
When looking up via iban or email, the lead must have exactly one actionable subscription (status in: ACTIVE, PAST_DUE, PAUSED, PENDING, PENDING_ACTIVATION). If multiple actionable subscriptions exist, the row is marked as ambiguous and skipped.