Android Paid App Developer Guide

Aprenda a adaptar su aplicación de pago de Android para que funcione con Pagos Web y brinde una mejor user experience a los clientes.

May 25, 2020

the Payment request API trae a la web una interfaz integrada basada en browser que permite a los usuarios ingresar la información de pago requerida más fácil que nunca. La API también puede invocar aplicaciones de pago específicas de la plataforma.

En comparación con el uso de solo Android Intents, los pagos web permiten una mejor integración con el navegador, la seguridad y la experiencia del Username:

• The payment application is launched as modal, in the context of the merchant's website.
• The implementation is complementary to your existing payment application, allowing you to take advantage of your user base.
• Payment app signature is checked to avoid
  lateral load.
• Payment apps can support multiple payment methods.
• Se puede integrar cualquier método de pago, como criptomonedas, transferencias bancarias y más. Las aplicaciones de pago en dispositivos Android pueden incluso integrar métodos que requieren acceso al chip de hardware en el dispositivo.

There are four steps required to implement web payments in an Android payment application:

1. Let merchants discover your payment application.
2. Informe a un comerciante si un client tiene un instrumento registrado (como una tarjeta de crédito) que está listo para pagar.
3. Let a customer make the payment.
4. Check the signing certificate of the caller.

To see web payments in action, see the
payment-web-android
manifestation.

Step 1: let merchants discover your payment app

For a merchant to use your payment application, they must use the Payment request API and specify the payment method you support using the payment method identifier.

If you have a unique payment method identifier for your payment app, you can set yours payment method manifest para que los browsers puedan descubrir su aplicación.

Step 2: Inform a merchant if a client has a registered instrument that they are ready to pay

The merchant can call hasEnrolledInstrument () to see if the customer can make a payment. You can implement IS_READY_TO_PAY as an Android service to answer this query.

AndroidManifest.xml

Declare your service with an intent filter with action
org.chromium.intent.action.IS_READY_TO_PAY.

<service
android:yam=".SampleIsReadyToPayService"
android:exported="true">
<intent-filter>
<action android:yam="org.chromium.intent.action.IS_READY_TO_PAY" />
</intent-filter>
</service>

the IS_READY_TO_PAY the service is optional. If there is no such intent handler in the payment application, then the web browser assumes that the application can always make payments.

AIDL

The API for IS_READY_TO_PAY el servicio está definido en AIDL. Cree dos archivos AIDL con el siguiente contents:

app / src / main / aidl / org / chromium / IsReadyToPayServiceCallback.aidl

package org.chromium;
interface IsReadyToPayServiceCallback {
oneway void handleIsReadyToPay(boolean isReadyToPay);
}

app / src / main / aidl / org / chromium / IsReadyToPayService.aidl

package org.chromium;
import org.chromium.IsReadyToPayServiceCallback;
interface IsReadyToPayService {
oneway void isReadyToPay(IsReadyToPayServiceCallback callback);
}

Implement IsReadyToPayService

The simplest implementation of IsReadyToPayService shown in the following example:

class SampleIsReadyToPayService : Service() {
private val binder = object : IsReadyToPayService.Stub() {
override fun isReadyToPay(callback: IsReadyToPayServiceCallback?) {
callback?.handleIsReadyToPay(true)
}
}
override fun onBind(I tried: Intent?): IBinder? {
return binder
}
}

Parameters

Pass the following parameters to onBind as Intent extras:

• methodNames
• methodData
• topLevelOrigin
• topLevelCertificateChain
• topLevelCertificateChain
• paymentRequestOrigin

override fun onBind(I tried: Intent?): IBinder? {
val extras: Bundle? = I tried?.extras
}

methodNames

The names of the methods that are queried. The elements are the keys in the
methodData dictionary and indicate the methods that the payment application supports.

val methodNames: List<String>? = extras.getStringArrayList("methodNames")

methodData

A mapping of each input of methodNames to the
methodData.

val methodData: Bundle? = extras.getBundle("methodData")

topLevelOrigin

The origin of the merchant without the schema (the origin without the schema of the top-level navigation context). For example, https://mystore.com/checkout it will pass like mystore.com.

val topLevelOrigin: String? = extras.getString("topLevelOrigin")

topLevelCertificateChain

La cadena de certificados del comerciante (la cadena de certificados del contexto de navegación de nivel superior). Nulo para localhost y archivo en disco, que son contextos seguros sin certificados SSL. La cadena de certificados es necesaria porque una aplicación de pago puede tener diferentes requisitos de confianza para los sitios web.

val topLevelCertificateChain: Array<Parcelable>? =
extras.getParcelableArray("topLevelCertificateChain")

Every Parcelable is a Bundle with a "certificate" key and a byte array value.

val list: List<ByteArray>? = topLevelCertificateChain?.mapNotNull { p ->
(p ace Bundle).getByteArray("certificate")
}

paymentRequestOrigin

El origen sin esquema del contexto de navegación de iframe que invocaba new PaymentRequest (methodData, details, options) constructor en JavaScript. Si el constructor fue invocado desde el contexto de nivel superior, entonces el valor de este parámetro es igual al valor de topLevelOrigin parameter.

val paymentRequestOrigin: String? = extras.getString("paymentRequestOrigin")

Answer

The service can send its response through handleIsReadyToPay (Boolean) method.

callback?.handleIsReadyToPay(true)

Excuse me

You can use Binder.getCallingUid () to check who the caller is. Note that you have to do this in the isReadyToPay method, not the onBind method.

override fun isReadyToPay(callback: IsReadyToPayServiceCallback?) {
try {
val callingPackage = packageManager.getNameForUid(Binder.getCallingUid())

See Verify the caller's signing certificate for how to verify that the calling packet has the correct signature.

Step 3: let a customer check out

The merchant calls Show() to start the payment application so that the customer can make a payment. The paid app is invoked through an Android intent PAY with transaction information in the intent parameters.

The payment application responds with methodName and details, which are specific to the payment application and are opaque to the browser. The browser converts the details
String in a JavaScript object for the merchant via JSON deserialization, but it doesn't apply any validity beyond that. The browser does not modify the
details; the value of that parameter is passed directly to the merchant.

AndroidManifest.xml

The activity with the PAY The intent filter must have a A tag that identifies the default payment method identifier for the application.

To support multiple payment methods, add a label with a
resource.

<activity
android:yam=".PaymentActivity"
android:theme="@style/Theme.SamplePay.Dialog">
<intent-filter>
<action android:yam="org.chromium.intent.action.PAY" />
</intent-filter>
<meta-data
android:yam="org.chromium.default_payment_method_name"
android:value="https://bobpay.xyz/pay" />
<meta-data
android:yam="org.chromium.payment_method_names"
android:resource="@array/method_names" />
</activity>

the resource debe ser una lista de cadenas, cada una de las cuales debe ser una Url absoluta válida con un esquema HTTPS como se muestra aquí.

<?xml version="1.0" encoding="utf-8"?>
<resources>
<string-array yam="method_names">
<item>https://alicepay.com/put/optional/path/here</item>
<item>https://charliepay.com/put/optional/path/here</item>
</string-array>
</resources>

Parameters

The following parameters are passed to the activity as intent extras:

• methodNames
• methodData
• topLevelOrigin
• topLevelCertificateChain
• paymentRequestOrigin
• total
• modifiers
• paymentRequestId

val extras: Bundle? = I tried?.extras

methodNames

The names of the methods that are used. The elements are the keys in the
methodData dictionary. These are the methods that the payment application supports.

val methodNames: List<String>? = extras.getStringArrayList("methodNames")

methodData

A mapping of each of the methodNames to the
methodData.

val methodData: Bundle? = extras.getBundle("methodData")

Merchant name

The content of the