« Back to Add-on Library
Authnet Endpoint
A lightweight, configurable WordPress endpoint that integrates Authorize.net payment tokenization with FileMaker solutions. Using Accept.js for secure client-side tokenization, Authnet Endpoint allows FileMaker WebViewers to collect payment information and generate single-use payment nonces for direct Authorize.net transactions. Card data never reaches your server or database.
### Payment Features
Accept.js Tokenization — Client-side payment tokenization using Authorize.net Accept.js library
Payment Nonce Generation — Secure single-use tokens for direct Authorize.net transactions
PCI-DSS Compliance — Card data never reaches your server or database
Sandbox & Live Modes — Seamless testing and production support (controlled by API credentials)
Custom Endpoint URL — Configurable slug for your payment endpoint
FileMaker Integration — Nonces passed directly to FileMaker script callbacks
Direct Transactions Only — Designed for charge-and-process workflows (not subscriptions or stored methods)
### Form Features
(or ACH details)
Payment Method Selection — Credit card and ACH transfer options
Field Validation — Client-side validation before tokenization
Error Display — User-friendly error messages for validation failures
Processing Indicator — Visual feedback during tokenization
Result Handling — Nonce returned to FileMaker via script callback
Result Display — Success/failure messages from FileMaker processing
### FileMaker Integration
WebViewer Support — Embed payment form in FileMaker layouts
Script Callbacks — Receive payment nonces in FileMaker scripts
Query Parameters — Pass credentials and configuration via URL
JavaScript Functions — Call Authorize.net operations from FileMaker
Result Handling — Display payment results to end users
### Admin Features
Settings Page — Configure endpoint slug
Integration Guide — Step-by-step FileMaker setup instructions
Code Examples — FileMaker script templates
Endpoint URL Viewer — See your active endpoint URL
Documentation — Complete reference for Accept.js and integration
### What's Included
✅ WordPress endpoint function snippet
✅ Credit card and ACH payment method support
✅ Full admin documentation and integration guide
✅ FileMaker script code examples
✅ Sample FileMaker database (Authnet Endpoint.fmp12)
✅ readme.txt with requirements and installation
### What's NOT Included (Separate Architecture Required)
❌ Customer profile creation (CIM) and management
❌ Payment profile storage for subscriptions or recurring charges
❌ Refund processing (nonce is single-use and consumed)
❌ Stored payment methods
❌ Recurring billing setup
✅ Sample FileMaker database (Authnet Endpoint.fmp12)
✅ readme.txt with requirements and installation
## Requirements
WordPress 5.Invoice Payments — One-time payment processing for invoices
Donation Processing — Secure donation collection from FileMaker WebViewers
Restaurant/Retail — Direct payment processing at point-of-sale
Multi-tenant Systems — Centralized payment system for FileMaker apps
Mobile WebViewer Apps — Payment forms in FileMaker Go/WebDirect
Custom Workflows — Integrate direct payments into business processes
NOT Ideal For:
Recurring billing or subscriptions (requires customer profiles)
Stored payment methods (nonce cAccept.js tokenizes card data in the browser before transmission
PCI-DSS Compliance — No sensitive card data stored, logged, or transmitted to your server
Nonce-Based Architecture — Single-use payment tokens minimize exposure window
HTTPS Required — Production endpoints must use SSL/TLS encryption
Accept.js Library — Authorize.net-approved and maintained secure tokenization library
No Card Storage — Cards processed, tokenized, and immediately discarded
## Technical Architecture
### Payment Floorize.net credentials (API Login ID, Client Key)
2. Import authnet-endpoint-1.0.0.json via CWP Snippets
3. Configure endpoint slug in WordPress settings (default: authnetpayment)
4. Add WebViewer to FileMaker layout with endpoint URL + credentials
5. Create FileMaker scripts to:
- Receive payment nonce from endpoint
- Call Authorize.net API to process the nonce
- Handle success/failure results
6. Use sample database as implementation reference
7. Test in Authorize.net sandbox environment
8. Deploy to production with live credentials and HTTPS
## Limitations & Constraints
Single-Use Nonce — Nonce expires/consumed after one transaction attempt
No Card Storage — Cart data not stored (endpoint stateless)
No Refund Capability — Cannot issue refunds with nonce alone (full card required)
No Subscriptions — Not designed for recurring billing or stored payment methods
No Profiles — Does not create Authorize.net customer profiles
Direct Only — Designed specifically for single-transaction direct payments
## When to Use Alternative Architecture
If you need any of these features, a different integration approach is required:
Subscriptions/Recurring → Authorize.net CIM (Customer Information Manager) with profile storage
Refunds → Store full card data + transaction IDs in secure database
Stored Methods → Customer payment profile system with vault implementation
Multiple Charges → Authorize.net recurring billing or subscription APIordPress setting
### Payment Profile Requirements (For Future Enhancement)
If building customer profile / recurring billing functionality:
Billing Address Required — Must be stored with payment profile in CIM
Customer Type Field — Accepts "individual" or "business" during profile creation
Full Card Data — Complete card number must be sent (not just last 4 digits)
Card Storage — Requires separate database system for PCI compliance
FileMaker E-commerce — Accept payments directly in FileMaker solutions
Donation Processing — Secure donation collection from FileMaker WebViewers
Invoice Payments — Allow customers to pay invoices via FileMaker portal
Multi-tenant Systems — Centralized payment system for FileMaker apps
Mobile WebViewer Apps — Payment forms in FileMaker Go/WebDirect
Custom Workflows — Integrate payments into business process designs
## Security Features
Client-Side Tokenization — Card data tokenized before transmission
PCI-DSS Compliance — No sensitive card data stored or logged
Accept.js Library — Authorize.net-approved secure tokenization
HTTPS Required — Production deployments must use SSL/TLS
Nonce-Based — Single-use payment tokens minimize exposure
No Card Storage — Cards processed and discarded per transaction
## Implementation Workflow
1. Request Authnet credentials (API Login ID, Client Key)
2. Import authnet-endpoint-1.0.0.json via CWP Snippets
3. Configure endpoint slug in WordPress settings
4. Add WebViewer to FileMaker layout with endpoint URL
5. Create FileMaker scripts to handle payment nonces
6. Reference sample database for implementation patterns
7. Test in Authorize.net sandbox environment
8. Deploy to production with live credentials
## Technical Notes
Endpoint returns standalone HTML form (no WordPress template)
Rewrite rules auto-flush when slug is changed
Query parameters: login (API Login ID), key (Client Key), script (FileMaker script name)
Payment nonce passed as parameter to specified FileMaker script
Works in FileMaker Pro, FileMaker Go, and FileMaker WebDirect
* Compatible with both iOS and Android WebViewer implementations
### Payment Features
Accept.js Tokenization — Client-side payment tokenization using Authorize.net Accept.js library
Payment Nonce Generation — Secure single-use tokens for direct Authorize.net transactions
PCI-DSS Compliance — Card data never reaches your server or database
Sandbox & Live Modes — Seamless testing and production support (controlled by API credentials)
Custom Endpoint URL — Configurable slug for your payment endpoint
FileMaker Integration — Nonces passed directly to FileMaker script callbacks
Direct Transactions Only — Designed for charge-and-process workflows (not subscriptions or stored methods)
### Form Features
(or ACH details)
Payment Method Selection — Credit card and ACH transfer options
Field Validation — Client-side validation before tokenization
Error Display — User-friendly error messages for validation failures
Processing Indicator — Visual feedback during tokenization
Result Handling — Nonce returned to FileMaker via script callback
Result Display — Success/failure messages from FileMaker processing
### FileMaker Integration
WebViewer Support — Embed payment form in FileMaker layouts
Script Callbacks — Receive payment nonces in FileMaker scripts
Query Parameters — Pass credentials and configuration via URL
JavaScript Functions — Call Authorize.net operations from FileMaker
Result Handling — Display payment results to end users
### Admin Features
Settings Page — Configure endpoint slug
Integration Guide — Step-by-step FileMaker setup instructions
Code Examples — FileMaker script templates
Endpoint URL Viewer — See your active endpoint URL
Documentation — Complete reference for Accept.js and integration
### What's Included
✅ WordPress endpoint function snippet
✅ Credit card and ACH payment method support
✅ Full admin documentation and integration guide
✅ FileMaker script code examples
✅ Sample FileMaker database (Authnet Endpoint.fmp12)
✅ readme.txt with requirements and installation
### What's NOT Included (Separate Architecture Required)
❌ Customer profile creation (CIM) and management
❌ Payment profile storage for subscriptions or recurring charges
❌ Refund processing (nonce is single-use and consumed)
❌ Stored payment methods
❌ Recurring billing setup
✅ Sample FileMaker database (Authnet Endpoint.fmp12)
✅ readme.txt with requirements and installation
## Requirements
WordPress 5.Invoice Payments — One-time payment processing for invoices
Donation Processing — Secure donation collection from FileMaker WebViewers
Restaurant/Retail — Direct payment processing at point-of-sale
Multi-tenant Systems — Centralized payment system for FileMaker apps
Mobile WebViewer Apps — Payment forms in FileMaker Go/WebDirect
Custom Workflows — Integrate direct payments into business processes
NOT Ideal For:
Recurring billing or subscriptions (requires customer profiles)
Stored payment methods (nonce cAccept.js tokenizes card data in the browser before transmission
PCI-DSS Compliance — No sensitive card data stored, logged, or transmitted to your server
Nonce-Based Architecture — Single-use payment tokens minimize exposure window
HTTPS Required — Production endpoints must use SSL/TLS encryption
Accept.js Library — Authorize.net-approved and maintained secure tokenization library
No Card Storage — Cards processed, tokenized, and immediately discarded
## Technical Architecture
### Payment Floorize.net credentials (API Login ID, Client Key)
2. Import authnet-endpoint-1.0.0.json via CWP Snippets
3. Configure endpoint slug in WordPress settings (default: authnetpayment)
4. Add WebViewer to FileMaker layout with endpoint URL + credentials
5. Create FileMaker scripts to:
- Receive payment nonce from endpoint
- Call Authorize.net API to process the nonce
- Handle success/failure results
6. Use sample database as implementation reference
7. Test in Authorize.net sandbox environment
8. Deploy to production with live credentials and HTTPS
## Limitations & Constraints
Single-Use Nonce — Nonce expires/consumed after one transaction attempt
No Card Storage — Cart data not stored (endpoint stateless)
No Refund Capability — Cannot issue refunds with nonce alone (full card required)
No Subscriptions — Not designed for recurring billing or stored payment methods
No Profiles — Does not create Authorize.net customer profiles
Direct Only — Designed specifically for single-transaction direct payments
## When to Use Alternative Architecture
If you need any of these features, a different integration approach is required:
Subscriptions/Recurring → Authorize.net CIM (Customer Information Manager) with profile storage
Refunds → Store full card data + transaction IDs in secure database
Stored Methods → Customer payment profile system with vault implementation
Multiple Charges → Authorize.net recurring billing or subscription APIordPress setting
### Payment Profile Requirements (For Future Enhancement)
If building customer profile / recurring billing functionality:
Billing Address Required — Must be stored with payment profile in CIM
Customer Type Field — Accepts "individual" or "business" during profile creation
Full Card Data — Complete card number must be sent (not just last 4 digits)
Card Storage — Requires separate database system for PCI compliance
FileMaker E-commerce — Accept payments directly in FileMaker solutions
Donation Processing — Secure donation collection from FileMaker WebViewers
Invoice Payments — Allow customers to pay invoices via FileMaker portal
Multi-tenant Systems — Centralized payment system for FileMaker apps
Mobile WebViewer Apps — Payment forms in FileMaker Go/WebDirect
Custom Workflows — Integrate payments into business process designs
## Security Features
Client-Side Tokenization — Card data tokenized before transmission
PCI-DSS Compliance — No sensitive card data stored or logged
Accept.js Library — Authorize.net-approved secure tokenization
HTTPS Required — Production deployments must use SSL/TLS
Nonce-Based — Single-use payment tokens minimize exposure
No Card Storage — Cards processed and discarded per transaction
## Implementation Workflow
1. Request Authnet credentials (API Login ID, Client Key)
2. Import authnet-endpoint-1.0.0.json via CWP Snippets
3. Configure endpoint slug in WordPress settings
4. Add WebViewer to FileMaker layout with endpoint URL
5. Create FileMaker scripts to handle payment nonces
6. Reference sample database for implementation patterns
7. Test in Authorize.net sandbox environment
8. Deploy to production with live credentials
## Technical Notes
Endpoint returns standalone HTML form (no WordPress template)
Rewrite rules auto-flush when slug is changed
Query parameters: login (API Login ID), key (Client Key), script (FileMaker script name)
Payment nonce passed as parameter to specified FileMaker script
Works in FileMaker Pro, FileMaker Go, and FileMaker WebDirect
* Compatible with both iOS and Android WebViewer implementations
Downloads
- Download v1.0.0 authnet-endpoint-1.0.0.zip