Skip to content
Merxian

Event catalogue

Every event that Merxian can send to your webhook endpoint. Each event page shows the cause, the payload, and an example.

On this page

Every event has the same envelope. The resource is indata.object, in the shape of its group. Subscribe to only the events that you use.

Checkout events#

Payload: the checkout_session object. Concept: Checkout sessions.

EventMerxian sends it when
checkout.createdYou created a checkout session, or a buyer opened a payment link.
checkout.completedThe payment of the session succeeded. This can happen after the session expiry time.
checkout.expiredThe session reached its expiry time, you expired it, or the buyer cancelled on the hosted page.

Transaction events#

Payload: the transaction object. Concept: Transactions.

EventMerxian sends it when
transaction.createdYou created a transaction, or a checkout session or payment link created one.
transaction.readyThe transaction moved from draft to ready. Its amounts are now frozen.
transaction.processingA payment of the transaction was created or is being processed.
transaction.completedPayments collected the full amount that the transaction requires.
transaction.canceledYou canceled the transaction, or a checkout session ended and canceled the draft that it created.
transaction.past_dueA ready or processing transaction reached its dueAt time and was not fully paid.
transaction.partially_refundedA refund succeeded and money is still collected on the transaction.
transaction.refundedRefunds returned all collected money.
transaction.adjustedYou added an adjustment, or Merxian recorded one, for example for a chargeback.

Payment events#

Payload: the payment object. Concept: Payments.

EventMerxian sends it when
payment.createdA checkout session or your call to Create a payment created a payment.
payment.processingMerxian sent the payment for processing and waits for the result.
payment.succeededThe payment was authorized and captured. Capture is automatic.
payment.failedThe payment was refused or could not be completed.
payment.canceledYou canceled the payment, or a checkout session ended while the payment was open.
payment.expiredThe payer did not complete the payment in time.

Refund events#

Payload: the refund object. Concept: Refunds.

EventMerxian sends it when
refund.succeededThe refunded money was sent back to the payer.
refund.failedThe refund could not be completed.
refund.reversedA refund was returned after it succeeded, so the money came back to your balance.

Dispute events#

Payload: the payment object. Concept: Disputes.

EventMerxian sends it when
dispute.openedThe payer's bank opened a dispute, such as a chargeback, on a payment.

Invoice events#

Payload: the invoice object. Concept: Invoices.

EventMerxian sends it when
invoice.issuedA paid transaction on a merchant of record account received its invoice.
invoice.creditedA refund or a correction reduced an invoiced amount.

Customer events#

Payload: the customer object. Concept: Customers.

EventMerxian sends it when
customer.createdOpt-inA customer was added to your account.
customer.updatedOpt-inA field of a customer changed.

State values in payloads

Webhook payloads use snake_case field names. Some state values in payloads differ from the values of the API. Compare them with this table.

ResourceAPI valueWebhook value
Transactiondraft, ready, … (lower case)DRAFT, READY, … (upper case)
Paymentcancelledcanceled
Refundrefundedsucceeded
Checkout sessioncompletecompleted

Try refund, payment.succeeded,POST /v1/transactions, orIdempotency-Key.