Paymend API documentation

One row per payment record created, regardless of whether it was later processed, declined or canceled. This is the widest of the four reports and the starting point of the reconciliation chain.

report_payments_created-{merchant_name}-{period_start}_to_{period_end}.csv

Bounded on event_created_at.

Columns

Column	Type	Description
`event_id`	string	Unique identifier for the payment. Used as `payment_id` in every other report.
`event_created_at`	timestamp	When the payment record was created. UTC, microsecond precision.
`event_type`	enum	Always `PAYMENT_CREATION`.
`merchant_name`	string	Your merchant identifier.
`store_id`	string	Store the payment belongs to, or `NA` where not configured.
`merchant_reference`	string	Your own reference, as supplied on the payment request. Empty when not provided.
`event_amount`	decimal	Payment amount in major units.
`currency`	string	ISO 4217 currency of the payment.
`consumer_first_name`	string	Consumer given name.
`consumer_last_name`	string	Consumer family name.
`consumer_email`	string	Consumer email address.
`card_brand`	enum	`VISA`, `MASTERCARD`, `AMEX`, `DISCOVER`.
`card_bin`	string	First 6-8 digits of the card number.
`card_last_4_digits`	string	Last four digits of the card number.

event_id here is the payment identifier. It appears as payment_id — not as event_id — in the transactions, disputes and settlement reports. Every other report uses event_id for its own event, not for the payment.

Creation does not imply processing

A row in this report means a payment record exists. It does not mean money moved. A payment may be created and never processed, processed days later, or processed across several attempts. Expect this report to contain more rows than the transactions report for the same period, and do not treat the difference as a reconciliation break. See the reconciliation guide for how to age unprocessed payments correctly.

Example

report_payments_created-my_merchant-20260801_to_20260810.csv

event_id,event_created_at,event_type,merchant_name,store_id,merchant_reference,event_amount,currency,consumer_first_name,consumer_last_name,consumer_email,card_brand,card_bin,card_last_4_digits
PAYM_7bQ2xKmR4v,2026-08-01 09:14:02.000000 UTC,PAYMENT_CREATION,my_merchant,store_abc,ORD-88213,49.00,USD,Priya,Raman,priya.raman@example.com,VISA,411111,4242
PAYM_Nc9wTdLs3E,2026-08-01 11:47:55.000000 UTC,PAYMENT_CREATION,my_merchant,store_123,ORD-88214,129.50,USD,Tomas,Lindqvist,t.lindqvist@example.com,MASTERCARD,555555,8081
PAYM_Hj4zVpQa8M,2026-08-02 16:02:19.000000 UTC,PAYMENT_CREATION,my_merchant,store_abc,,49.00,USD,Awa,Diallo,awa.diallo@example.com,VISA,400005,1907
PAYM_Ry6kBnXu2W,2026-08-03 03:31:40.000000 UTC,PAYMENT_CREATION,my_merchant,store_123,ORD-88219,24.95,USD,Hannah,Byrne,hbyrne@example.com,AMEX,371449,6003

Process payments

Payments created

Columns

Creation does not imply processing

Example

​Columns

​Creation does not imply processing

​Example

Columns

Creation does not imply processing

Example