.payment-service-definition {
    background-color: white !important;
    border: 1px solid #0a0e0d1a;
    border-radius: 16px;
    padding: 2em;
    vertical-align: middle;
}

.payment-service-definition img {
    margin: 0 1em 0 0;
    max-width: 3em;
    display: inline-block;
}

.payment-service-definition h2 {
    margin: 0;
    display: inline-block;
    position: relative;
    top: 0.1em;
} 

Events

Webhook events

mattilda Pay

Grow your payment capabilities with code.

Overview

Getting started with mattilda Pay

Command Line Interface (CLI)

Postman

Postman Collection

High level transaction insights with a daily, weekly, or monthly view.

Insights

A data dashboard that allows you to deep dive into your payments data

Authorizations

Authorization Insights

Generate and schedule transactions via the dashboard.

Reports

The specification of a report as defined by the API.

Specification

Report specification

Learn how to create a report via the dashboard.

Setup

Setup a report

API authentication basics and best practices.

Authentication

JWTs

Authentication with JWTs

Sandbox and Production environments within an instance.

Environments

Best practices on handling errors and other exceptions.

Errors

Error handling

Best practices on handling retries in an idempotent way.

Idempotent Requests

Best practices on handling the original IP address for a transaction.

IP Address Forwarding

Best practices on handling pagination in the API.

Pagination

Rate limiting

Returns a paginated list of transactions for the merchant account, sorted by most recently updated. You can filter, sort, and search transactions using query parameters.

List transactions

Create a new transaction using a supported payment method. If additional buyer authorization is required, an approval URL will be returned. Duplicated gift card numbers are not supported.

Create transaction

Retrieve the details of a transaction by its unique identifier.

Get transaction

Captures a previously authorized transaction. You can capture the full or a partial amount, as long as it does not exceed the authorized amount (unless over-capture is enabled).

Capture transaction

Voids a previously authorized transaction. If the transaction was not yet successfully authorized, or was already captured, the void will not be processed. This operation releases the hold on the buyer's funds. Captured transactions can be refunded instead.

Void transaction

Retrieve a paginated list of events related to processing a transaction, including status changes, API requests, and webhook delivery attempts. Events are listed in chronological order, with the most recent events first.

List transaction events

Synchronizes the status of a transaction with the underlying payment service provider. This is useful for transactions in a pending state to check if they've been completed or failed. Only available for some payment service providers.

Sync transaction

List all buyers or search for a specific buyer.

List all buyers

Add a buyer

Get a buyer

Update a buyer

Delete a buyer

Create checkout session

Retrieve the information stored on a checkout session.

Get checkout session

Update the information stored on a checkout session.

Update checkout session

Deleta a checkout session and all of its (PCI) data.

Delete checkout session

Update session fields

List all payment links

Add a payment link

Get payment link

Expire a payment link

List the payment options available at checkout. filtering by country, currency, and additional fields passed to Flow rules.

List payment option

List payment options

List transaction refunds

Create transaction refund

Create a refund for all instruments on a transaction.

Refund all instruments

Create batch transaction refund

Get refund

Creates a session for a payment service that supports sessions.

Get session

Create a session for apayment service definition

Get session by ID

Client errors

Client-side errors (4XX)

Server errors

Server-side errors (5XX)

List 4XX errors

square-terminal

The latest product news, changes, and other announcements

Latest

Updates & Announcements

Csharp

Java

Python

Typescript

How scalable payments flow

Embed events

Locales

Embed localization

Theming

Embed Theming

Options

Embed options

In-app browsers

In-app browsers with Embed

Common issues

Common issues with Embed

Use Secure Fields to collect the CVV for cards previously stored.

Stored cards

Secure Fields with stored cards

Each field can be customized to match your brand using the `styles` property
when adding the field.

Secure Fields theming

Secure Fields events

Secure Fields and 3DS

Vault token import

Import file

Token import file creation

Upload tokens

Token import file upload

Buyers & payment methods

Creating buyers & payment methods on import

Vault Forward

Enable endpoint

Enable a Vault Forward endpoint

Forward to endpoint

Vault Forward card data to API endpoint

CVV & Secure Fields

Vault Forward card data from a checkout session

Homepage

Dashboard Homepage

3-D Secure

Setup 3-D Secure

Embed

3-D Secure in Embed

Hosted via API

Hosted 3-D Secure

External 3DS server

External 3-D Secure server

Testing

3-D Secure Testing

Account Updater

Manual updates

Manual account updates

Scheduled updates

Scheduled account updates

Anti-fraud

Fingerprints

Automatic anti-fraud device fingerprinting

Reviews

Anti-fraud reviews

Simulator

Anti-fraud simulator

Apple Pay

Web with Embed

Apple Pay on web with Embed

Web without Embed

Apple Pay on web without Embed

iOS with SDK

Apple Pay on iOS with the SDK

iOS without SDK

Apple Pay on iOS without the SDK

Decrypted tokens

Decrypted Apple Pay tokens

Google Pay

Google Pay on web with Embed

Google Pay on web without Embed

Android with SDK

Google Pay on Android with the SDK

Android without SDK

Google Pay on Android without the SDK

Decrypted Google Pay tokens

Create transactions without a creating a buyer first

Guest checkout

Use guest buyer details in combination with stored buyer records and their payment methods

Resource	Payload `name`	Description
Buyer	`buyer.created`	A buyer was created successfully.
Buyer	`buyer.updated`	A buyer was updated successfully. This does not include it’s shipping details, see `shipping-details.deleted`.
Buyer	`buyer.deleted`	A buyer was deleted.
Payment method	`payment-method.paused`	A stored payment method (e.g. card) was paused.
Payment method	`payment-method.resumed`	A stored payment method (e.g. card) was resumed.
Payment method	`payment-method.updated`	A stored payment method (e.g. card) was updated, likely due to an account update.
Payment method	`payment-method.deleted`	A stored payment method (e.g. card) was deleted, likely due to an update from the payment service.
Refund	`refund.declined`	A refund for a transaction was declined by the payment service.
Refund	`refund.failed`	A refund for a transaction was otherwise rejected by the payment service.
Refund	`refund.pending`	A refund for a transaction is pending.
Refund	`refund.succeeded`	A refund for a transaction succeeded.
Report execution	`report-execution.failed`	A report failed to generate.
Report execution	`report-execution.succeeded`	A report was generated.
Shipping details	`shipping-details.created`	A buyer successfully had it’s shipping details added.
Shipping details	`shipping-details.updated`	A buyer’s shipping details were updated successfully.
Shipping details	`shipping-details.deleted`	A buyer’s shipping details were deleted.
Transaction	`transaction.authenticated`	A transaction was successfully authenticated.
Transaction	`transaction.authentication-pending`	A transaction is pending authentication.
Transaction	`transaction.authorized`	A transaction is authorized (through 3DS or otherwise) but has not yet been authenticated.
Transaction	`transaction.capture-failed`	An authorized transaction failed to capture.
Transaction	`transaction.capture-pending`	An authorized transaction is pending capture.
Transaction	`transaction.captured`	An authorized transaction was captured.
Transaction	`transaction.declined`	A transaction was declined.
Transaction	`transaction.failed`	A transaction failed due to an internal or external reason. Please check the `error_code` for the cause.
Transaction	`transaction.review-accepted`	A transaction that was held in anti-fraud review has been accepted but it’s status has not changed, only the `pending_review` property has been set to `false`.
Transaction	`transaction.void-declined`	An authorized transaction had it’s request to void the authorization declined by the payment service.
Transaction	`transaction.void-failed`	An authorized transaction had it’s request to void the authorization otherwise rejected by the payment service.
Transaction	`transaction.void-pending`	An authorized transaction has a pending void request.
Transaction	`transaction.voided`	An authorized transaction has been voided.

Getting Started

Integration

Tools

Cloud Vault

Features

Other

Webhook events