Apple Messages payments and sign-in setup
Configure interactive Apple Messages sign-in and Apple Pay requests with your identity and payment integrations.
What it is
OAuth Flow Setup and Apple Pay Setup add interactive requests to a connected Apple Messages account. A configured task can ask a customer to sign in through an identity service or respond to an Apple Pay request. Completing these actions depends on the identity or payment integration arranged for your account.
Who uses it and why
- Administrators arrange the merchant and identity-service accounts with Powerfront.
- Developers coordinate the identity and payment processing integrations.
- Operators follow the configured conversation flow and review the resulting replies.
- Visitors respond to the interactive request on a supported Apple device.
Where to find it
Powerfront manages OAuth Flow Setup and Apple Pay Setup within the Apple Messages account under Settings › General Settings › Integrations. Requests and replies appear in the Apple Messages conversation.
How it works
For sign-in, a configured task sends an interactive request tied to the current customer and conversation. INSIDE checks whether the device supports the required authentication control. If it does not, INSIDE skips the step and adds a comment for operators.
The customer follows the configured authorisation flow. INSIDE then needs the matching request context and the account's integration processing to handle the response. The request context lasts ten minutes. Missing or expired context prevents completion.
For Apple Pay, INSIDE creates an interactive payment request using the configured merchant identity and certificate. The configured payment connection handles the payment exchange. Payment replies can enter the conversation as a distinct response.
Treat the merchant's payment processing result as the authority for payment completion. A sent request or a reply in the transcript alone does not establish that funds have settled.
Configure it
Ask Powerfront to agree the identity and payment flows with your developer before enabling the corresponding task.
For sign-in, Powerfront configures OAuth Client Id, OAuth Client Secret, OAuth Client Response Type and OAuth Client Scope. The requested scope is a comma-separated list. These fields have no preset values.
For Apple Pay, Powerfront configures Merchant Name, Merchant Id, Merchant Certificate (Base64 Encoded) and, where needed, Merchant Certificate Password. These fields have no preset values. Payment Gateway Url can select a separate payment connection. Leaving it empty selects the INSIDE handoff, which still requires payment processing to be configured.
Fields
| Field | Where | Required | What it is for |
|---|---|---|---|
| OAuth Client Id | Settings › General Settings › Integrations | No | Identifies the application used by the configured sign-in flow. |
| OAuth Client Secret | Settings › General Settings › Integrations | No | Supplies the application's credential for the sign-in integration. |
| OAuth Client Response Type | Settings › General Settings › Integrations | No | Sets the response type requested from the identity service. |
| OAuth Client Scope | Settings › General Settings › Integrations | No | Lists the identity-service permissions requested by the sign-in flow, separated by commas. |
| Merchant Name | Settings › General Settings › Integrations | No | Supplies the merchant name required to send an Apple Pay request. |
| Merchant Id | Settings › General Settings › Integrations | No | Identifies the Apple Pay merchant required for payment requests. |
| Payment Gateway Url | Settings › General Settings › Integrations | No | Selects the payment processing connection. If empty, the INSIDE payment handoff is used and still needs a configured payment integration. |
| Merchant Certificate (Base64 Encoded) | Settings › General Settings › Integrations | No | Supplies the merchant certificate required for Apple Pay requests, entered or uploaded through the certificate control. |
| Merchant Certificate Password | Settings › General Settings › Integrations | No | Allows the configured merchant certificate to be opened when it is password protected. |
Limits and good to know
- Ordinary Apple messaging does not require these optional account sections.
- A generic authentication request is not a substitute for the configured Apple interactive sign-in flow.
- Sign-in depends on device support, a current request and working integration processing.
- These controls do not provide a general payment administration screen for settlement or refunds.
Depends on and works with
View all connections as a list
This feature uses
- Messaging channel connectionsConfigured by
Powerfront manages the account's OAuth and merchant connection details.
- Virtual Assistant tasks in messaging channelsRequires
Interactive sign-in and payment requests use configured Apple Messages tasks.
- Apple Messages conversationsRequires
Interactive sign-in and Apple Pay requests use an Apple Messages conversation and connected business account.
- Custom integrationsConfigured by
Powerfront's custom integration processes sign-in responses and the built-in payment handoff.
Used by
- Apple Messages conversationsEnhances
Separate integration setup enables interactive authentication and Apple Pay requests.
FAQ and troubleshooting
Why was the sign-in request skipped?
The customer's device did not report support for the required authentication control. Review the operator-visible comment and use your agreed alternative identity process.
Why did sign-in fail after the customer took a long time?
The matching request context lasts ten minutes. Ask Powerfront to check the flow and, where appropriate, start a fresh request.
Why won't an Apple Pay request send?
Ask Powerfront to check the merchant name, merchant identity and certificate, including its password where needed. The request needs valid merchant configuration.
Does a payment reply mean that payment is complete?
Confirm the result with your configured payment processor. The conversation records the exchange, while payment processing determines the financial outcome.