Commerce integration agent skills
Commerce integration agent skills give your compatible AI coding agent instructions and reference material for working with supported J.P. Morgan Commerce APIs. The skills can help you complete onboarding tasks, prepare your project and credentials, configure OAuth authentication, add an API integration, and receive webhook notifications.
You can follow the main guided workflow or run an individual skill after you’ve completed its prerequisites. The current offering supports Checkout, Online Payments, Tokenization, standalone 3-D Secure, and Account Updater.
The skills help you find and apply relevant Payments Developer Portal guidance while you work in your project. You remain in control of proposed changes and are responsible for reviewing and testing the resulting implementation.
Guided integration workflow
For the complete guided integration workflow, use these skills in order:
| Step | Skill | When to use it | What it helps you do |
|---|---|---|---|
| 1. Prepare your project | jpm-integrations-get-started |
Use this skill when you’re starting a J.P. Morgan integration or migrating from another payment provider. | Confirm your integration goal and onboarding status, check the credential files available to your project, and prepare the environment variables used by the remaining skills. |
| 2. Configure OAuth authentication | jpm-oauth |
Use this skill after you have the required onboarding credentials. | Generate an authentication module for your programming language that signs a JSON Web Token, exchanges it for an access token, and reuses the access token until shortly before it expires. |
| 3. Add a Commerce API integration | jpm-merchant-integrations |
Use this skill after you’ve configured J.P. Morgan authentication. | Add a supported Commerce API integration to your project after you’ve configured J.P. Morgan authentication. |
Select a skill name to review its current instructions in GitHub.
Each skill can run independently after you’ve completed its prerequisites. If you haven’t completed a prerequisite, the skill directs you to the appropriate earlier step.
Additional skills
The repository also provides standalone and companion skills that you can use when they apply to your integration.
| Skill | When to use it | What it helps you do | How it works with other skills |
|---|---|---|---|
jpm-csr |
Use this standalone skill before onboarding when you don’t yet have the required credentials. | Generate a Certificate Signing Request and private key to provide to your J.P. Morgan Relationship Manager for client ID provisioning. | This skill works independently from the guided integration workflow. |
jpm-notifications |
Use this companion skill after you’ve configured authentication and need to receive webhook events. | Receive and verify inbound J.P. Morgan webhook events, including signature verification, optional mutual TLS, and duplicate event handling. | This skill complements jpm-merchant-integrations and requires authentication configured through jpm-oauth. |
Supported API coverage
| API or capability | What the skills cover | Availability |
|---|---|---|
| Checkout | Drop-in UI, Hosted Payments Page, checkout sessions, capture methods, and field constraints | Available |
| Online Payments | Authorization, capture, void, refund, supported payment methods, and inline 3-D Secure | Available |
| Tokenization | Replace a card PAN with a merchant scoped token so you can store the token instead of card data | Early access |
| Standalone 3-D Secure | Add standalone 3-D Secure authentication when you aren’t using the inline threeDS field with an Online Payments authorization | Early access |
| Account Updater | Keep stored cards current through inquiry mode or card registration mode | Early access |
Next steps
1. Add the skills to your AI agent
Follow the setup instructions to add the skills to a compatible AI coding agent.
2. Use the skills
Start the guided integration workflow or invoke an individual skill after you’ve completed its prerequisites.
3. Review and test your integration
Review proposed code and configuration changes, confirm that the implementation follows current Payments Developer Portal guidance, and test it before production use.
Review and test your integration
Resources
Visit GitHub for the current installation instructions, usage guidance, source files, and supporting references.