Push to Wallet
Mobile Wallets are digital wallets held on mobile devices that transact with merchants by turning Native Card Primary Account Numbers (PANs) into digital tokens (e.g. for use with Apple Pay, G
Push
POST
https://api.synapsefi.com/v3.1/users/:user_id/nodes/:node_id/subnets/:subnet_id/push
This endpoint allows you generate a token to push card to digital wallet.
Path Parameters
subnet_id
string
ID of the subnet.
node_id
string
ID of the node.
user_id
string
ID of the user.
Headers
X-SP-USER
string
User's OAuth key and device fingerprint, separated by a pipe.
X-SP-USER-IP
string
IP address of user's device.
X-SP-GATEWAY
string
Your Client ID and Secret, separated by a pipe.
Request Body
type
string
Instant provisioning type. Can be set as APPLE_PUSH
, GOOGLE_PUSH
, or SAMSUNG_PUSH
.
nonce
string
Base64-encoded nonce provided by Apple.
nonce_signature
string
Base64-encoded nonce signature provided by Apple.
certificates
string
Array of 2 certificates provided by Apple.
Example Request
Notes on Apple Pay
Below is an overview of the data you must pass from Synapse's API response to Apple's PKAddPaymentPassRequest
:
activationData
: This is theactivation_data
returned in Synapse's API response.encryptedPassData
: This is theencrypted_data
returned in Synapse's API response.ephemeralPublicKey
: This is thepublic_key
returned in Synapse's API response.
Notes on Google Pay
The Opaque Payment Card ('OPC') object is a combination of the encrypted_data
and activation_data
returned in Synapse's API response, and can be constructed as follows:
Here is an example:
Once you have the OPC object, you should encode it as Base64. The above object would be:
Finally, this is the call your app would make to Google:
Last updated
Was this helpful?