method
to payto
and the redirect_url
to the endpoint of your application that can handle the customer returning once they’ve completed approving the transaction on payto.wpay.io
.
See the POST /transactions
API endpoint for more details.
intent
must be set to capture
.status
set to buyer_approval_pending
as well as a payment_method.approval_url
.
payment_method.approval_url
. After they’ve
authenticated themselves, the customer will be redirected back to the redirect_url
that you set when creating the transaction.
redirect_url
will be appended with the transaction_id
.
transaction_status
in this callback, it’s
recommended to also fetch the latest status via the API, as the status may
have changed since.store=true
parameter to each request to vault a PayTo agreement for future use.
Once stored, you can use the vaulted PayTo instrument for future transactions.
payto
and the redirect_url
to the endpoint
of your application that can handle the customer returning once they’ve completed setting up PayTo.
Please note that when using PayTo intent must be set to capture as delayed capture is not supported by PayTo.
See the POST /payment-methods
API endpoint for more details.
status
set to buyer_approval_pending
as well as a payment_method.approval_url
.
approval_url
.
After they’ve completed the required steps, the customer will be redirected back to the redirect_url
that
you set when creating the payment method.
GET /payment-methods
API endpoint for more details.