01
Apple Developer
Create the identity configuration.
- Register an App ID with Sign in with Apple.
- Create a Services ID for the website or app login.
- Add the domain and the correct return URL.
- Generate and securely download a Sign in with Apple key.
Sign in with Apple
Give customers an Apple sign-in path into ordering.
Add Sign in with Apple to your Ordering.co website and Customer App. Your team creates the identifiers and key in Apple Developer, then connects them in Ordering.co Social login options.
The customer experience
One familiar route from sign-in to ordering.
The customer sees Apple beside the other account options you enable. The configured Apple callback connects that authentication step back to your ordering experience.
- 01
Choose Apple
Customers select Continue with Apple from the sign-in options in your ordering experience.
- 02
Authenticate with Apple
Apple handles the account authentication before returning the customer through the configured callback.
- 03
Continue ordering
The customer returns to the website or Customer App and continues with the account connected to that sign-in.
Two connected workspaces
Configure Apple first. Connect Ordering.co second.
The identifiers must describe the same app, website, and return path in both systems. This is what allows Apple to return the customer to the correct ordering experience.
02
Ordering.co Dashboard
Connect the Apple identifiers.
- Open Settings → Pro → Social login options → Apple Sign-in.
- Enter the Team ID, Login ID, private key, Key ID, and Bundle ID.
- Set Enable Apple Login to Yes so the sign-in option is visible.
- Save, then test the complete sign-in return path.
Credential map
Know which Apple value belongs in each field.
Keep the private key secret. Apple permits a Sign in with Apple key file to be downloaded once, so store it in an approved secure location.
- Apple Team ID
- Apple Developer membership details
- Apple Login ID
- The Services ID identifier
- Apple Private Key
- The downloaded Sign in with Apple key
- Apple Private ID
- The Key ID associated with that private key
- Apple Bundle ID
- The app identifier registered with Apple
Before launch
Match the route, credentials, and customer surface.
The setup succeeds only when Apple Developer and Ordering.co use the same identifiers and approved return path.
Review Apple’s web requirements- Use the right callback. Standard websites use
/login/apple/callback; franchise websites use/searchlogin/apple/callback. - Protect the key. Treat the private key as a secret; never place it in tickets, chat, browser code, or public documentation.
- Enable the option. Saving credentials without enabling Apple Login leaves the customer button hidden.
- Test every intended surface. Confirm the complete sign-in and return flow on the website and Customer App you plan to launch.
Connect Apple sign-in to the customer account experience you operate.
Align the Apple identifiers, Ordering.co settings, and customer surfaces before launch.