Integrate the PayButton – Android

Du er her:
Anslået læsetid: 2 min


The PayButton requires minSdkVersion 17 and compileSdkVersion 26.

Add our repository to your project’s build.gradle:

allprojects {
    repositories {
        maven {
            url ""

Add the following exclusion rules to your module’s build.gradle (inside the android section):

packagingOptions {
    exclude 'META-INF/DEPENDENCIES.txt'
    exclude 'META-INF/LICENSE.txt'
    exclude 'META-INF/NOTICE.txt'
    exclude 'META-INF/LICENSE'
    exclude 'META-INF/NOTICE'
    exclude 'LICENSE.txt'
    exclude 'asm-license.txt'
    exclude 'META-INF/ASL2.0'

Add the libraries to the dependencies section of your module’s build.gradle:

dependencies {
    implementation ''
    implementation ''
    implementation ''
    implementation ''

    implementation ''

    // Add these three dependencies if you want to use a Miura card reader
    implementation ''
    implementation ''
    implementation ''

    // Add these two dependencies if you want to use a Verifone card reader
    implementation ''
    implementation ''

Peform a payment

This is how you start a payment in mock mode:

void paymentButtonClicked() {
    MposUi ui = MposUi.initialize(this, ProviderMode.MOCK,
            "merchantIdentifier", "merchantSecretKey");

            // Add this line, if you do want to offer printed receipts
            // MposUiConfiguration.SummaryFeature.PRINT_RECEIPT,
    // Start with a mocked card reader:
    AccessoryParameters accessoryParameters = new AccessoryParameters.Builder(AccessoryFamily.MOCK)
    // Add this line if you would like to collect the customer signature on the receipt (as opposed to the digital signature)
    // ui.getConfiguration().setSignatureCapture(MposUiConfiguration.SignatureCapture.ON_RECEIPT);
    /* When using the Bluetooth Miura, use the following parameters:
    AccessoryParameters accessoryParameters = new AccessoryParameters.Builder(AccessoryFamily.MIURA_MPI)
    /* When using Verifone readers via WiFi or Ethernet, use the following parameters:
    AccessoryParameters accessoryParameters = new AccessoryParameters.Builder(AccessoryFamily.VERIFONE_VIPA)
                                                                     .tcp("", 16107)
    TransactionParameters transactionParameters = new TransactionParameters.Builder()
                                                            .charge(new BigDecimal("5.00"), io.mpos.transactions.Currency.EUR)
                                                            .subject("Bouquet of Flowers")
    Intent intent = ui.createTransactionIntent(transactionParameters);
    startActivityForResult(intent, MposUi.REQUEST_CODE_PAYMENT);

The result is then delivered to your activity:

protected void onActivityResult(int requestCode, int resultCode, Intent data) {

    if (requestCode == MposUi.REQUEST_CODE_PAYMENT) {
        if (resultCode == MposUi.RESULT_CODE_APPROVED) {
            // Transaction was approved
            Toast.makeText(this, "Transaction approved", Toast.LENGTH_LONG).show();
        } else {
            // Card was declined, or transaction was aborted, or failed
            // (e.g. no internet or accessory not found)
            Toast.makeText(this, "Transaction was declined, aborted, or failed",
        // Grab the processed transaction in case you need it
        // (e.g. the transaction identifier for a refund).
        // Keep in mind that the returned transaction might be null
        // (e.g. if it could not be registered).
        Transaction transaction = MposUi.getInitializedInstance().getTransaction();

More information on the completed transaction statuses and what they mean can be found here.

Use a real card reader

You can then retrieve your merchantIdentifier and merchantSecretKey through the API and change the ProviderMode to ProviderMode.TEST.
Then create the AccessoryParameters with the reader family and connection you want to use.

Load merchant data 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, request the data from the API.
You can then fetch this data before a transaction and configure the PayButton correctly:

MposUi ui = MposUi.initialize(this, ProviderMode.TEST or ProviderMode.LIVE, 
loaded from the Yourpay API, 
MerchantIdentifier loaded from your backend, 
MerchantSecretKey loaded from the Yourpay API);

Receipt customization

You are required to offer an email or printed payment receipt to the shopper. The PayButton therefore allows the merchant to send an email payment receipt right after a transaction.

You might want to prevent this behavior, e.g. if you send your own receipts already and just want to append the required payment data. You can disable the built-in email receipts by removing MposUiConfiguration.SummaryFeature.SEND_RECEIPT_VIA_EMAIL from the setSummaryFeatures EnumSet.
If you choose to remove this, you must implement another way for the merchant to send out a receipt.