Welcome to the Developer Portal

Default UI Integration
- Integrating Default UI
- Migrating from PayButton to Default UI
- Managing Default UI Properties
- Summary Screen
- Incremental Authorization
- Custom Receipt Printing
- Automatic Receipt Printing
- Standalone Receipt Printing
- Sending Receipts via Email
- Customization
- Mobile UI Customization
- Release Notes

PayButton Integration
- Integration
- Stripe Transactions
- Alipay
- Summary Screen
- On-Reader Tipping
- Tip Adjust
- Loyalty and Bonus Cards
- Pre-Auth and Capture
- Refunds
- Custom Receipts
- Testing
- Going Live
- Release Notes

Custom Integration
- Installation
- Integration
- Stripe Transactions
- Signature
- Refunds
- Email & Print Receipts
- Custom Receipts
- Custom Receipts for PAX Terminals
- Preformatted Receipts
- Alipay
- On-Reader Tipping
- Tip Adjust
- Loyalty & Bonus Cards
- Pre-Auth & Capture
- Connection Keep-Alive
- Testing
- Going Live

Backend Integration
- API Endpoints and Authentication
- WebHooks
- Query Transactions
- Refunds
- Custom Receipts
- Going Live
- API Documentation

Card Readers
- Protecting Cardholder Data
- Developer Kits
- Test Cards
- Manage Card Readers
- Verifone Card Readers
  - Verifone e355
    - USB Connectivity Configuration
    - WiFI Connectivity Configuration
    - Windows Setup
    - User Guide
    - FAQ
  - Verifone P400
    - Getting Started with the Verifone P400
    - Ordering Test Equipment
    - Inspecting the Terminal
    - Connecting Verifone P400 Terminal Hardware
    - Configuring Ethernet Connectivity
    - Configuring USB Connectivity
    - Finding the Network Address Assigned to the Terminal
    - Configuring the Static IP Address
    - Verifying the Terminal IP Address
    - Changing Your Password on the Terminal
    - Processing a Transaction
    - Troubleshooting Terminal Issues
  - Verifone VX820
    - USB Connectivity Configuration
    - Ethernet Connectivity Configuration
    - Windows Setup
    - User Guide
    - FAQ
- Miura Card Readers
  - USB Connectivity Configuration
  - Windows Setup
  - Customization
  - Troubleshooting

Merchant Setup
- AMEX Merchant Setup
- Barclaycard APACS Merchant Setup
- Barclaycard HISO Merchant Setup
- Credorax Merchant Setup
- Elavon Merchant Setup
- EVRY Merchant Setup
- net-m Privatbank Merchant Setup
- Nexi Merchant Setup
- Stripe Merchant Setup
  - Stripe Direct and Stripe Connect
  - Stripe Connect

Storing Merchant Data on Your Backend

Right now, you have hardcoded the

merchantIdentifier

and

merchantSecretKey

. This means that all payments would be routed to the same merchant.

For a live solution, you might want to support multiple merchants, e.g. two different restaurants, to route the payment correctly. To support multiple merchants, store the following data on your backend:

merchantIdentifier

and

merchantSecretKey

. They identify to which merchant the payment is routed. You can create new merchants and get their credentials in the Gateway Manager.

Whether the merchant is a

TEST

or

LIVE

merchant.

You can then fetch this data before a transaction and configure the SDK correctly:

MPTransactionProvider* transactionProvider = 
        [MPMpos transactionProviderForMode::<TEST or LIVE, loaded from your backend:<
        merchantIdentifier::<MerchantIdentifier loaded from your backend:<
        merchantSecretKey::<MerchantSecretKey loaded from your backend:< ];

Right now, you have hardcoded the

merchantIdentifier

and

merchantSecretKey

. This means that all payments would be routed to the same merchant.

For a live solution, you might want to support multiple merchants, e.g. two different restaurants, to route the payment correctly. To support multiple merchants, store the following data on your backend:

merchantIdentifier

and

merchantSecretKey

. They identify to which merchant the payment is routed. You can create new merchants and get their credentials in the Gateway Manager.

Whether the merchant is a

TEST

or

LIVE

merchant.

You can then fetch this data before a transaction and configure the SDK correctly:

final TransactionProvider transactionProvider = Mpos.createTransactionProvider(this, 
        <TEST or LIVE, loaded from your backend>, 
        <MerchantIdentifier loaded from your backend>,
        <MerchantSecretKey loaded from your backend>);