Create Apple Pay session
Create a session with Apple Pay to facilitate a payment.
Read our Apple Pay tutorial to learn more. A successful response from this endpoint should be passed through to Apple Pay unchanged.
To access this endpoint using an access token
you’ll need to specify the /accounts/{accountID}/apple-pay.write
scope.
|
|
Stringified session object returned from Apple Pay.
The string value should be deserialized as a JSON object before passing to Apple.
"{\"epochTimestamp\":1733783167685,\"expiresAt\":1733786767685...}"
Response headers
x-request-id
string
<uuid>
required
{
"error": "string"
}
Response headers
x-request-id
string
<uuid>
required
Response headers
x-request-id
string
<uuid>
required
Response headers
x-request-id
string
<uuid>
required
Response headers
x-request-id
string
<uuid>
required
{
"error": "string"
}
Response headers
x-request-id
string
<uuid>
required
{
"error": "string"
}
Response headers
x-request-id
string
<uuid>
required
Response headers
x-request-id
string
<uuid>
required
Response headers
x-request-id
string
<uuid>
required
Response headers
x-request-id
string
<uuid>
required
Headers
x-moov-version
string
API version
Specify an API version.
API versioning follows the format vYYYY.QQ.BB
, where
YYYY
is the yearQQ
is the two-digit month for the first month of the quarter (e.g., 01, 04, 07, 10)BB
is the build number, starting at.01
, for subsequent builds in the same quarter.- For example,
v2024.01.00
is the initial release of the first quarter of 2024.
- For example,
The latest
version represents the most recent development state. It may include breaking changes and should be treated as a beta release.
v2024.01.00
Path parameters
accountID
string
<uuid>
required
Body
displayName
string
<=64 characters
required
domain
string
required
Response
Stringified session object returned from Apple Pay.
The string value should be deserialized as a JSON object before passing to Apple.